[Bug]: QR Codes Generated on T-Deck for Channels Produce Invalid Links Due to Incorrect PSK Encoding
I maintainer di solito rispondono entro 1 giorno
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Category
Other
Hardware
T-Deck
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
- Meshtastic UI aka MUI colorTFT
- InkHUD ePaper
- OLED slide UI on any display
Firmware Version
2.7.2 / 2.7.3
Description
QR codes for channels generated on the T-Deck device runing the Meshtastic User Interface (MUI) produce invalid links that incorrectly encode the channel's Pre-Shared Key (PSK). Instead of properly serializing the full channel settings (including name, PSK, and other configurations) into a base64url-encoded protobuf as required by Meshtastic's format, the T-Deck appears to only include a modified version of the PSK string directly in the link.
Specifically:
- The special character
/in the PSK is replaced with_. - The special character
+in the PSK is replaced with-. - The trailing
=(padding) in the PSK is omitted.
This results in an invalid QR code that cannot be scanned by the Meshtastic app on another node, as the link does not conform to the expected protobuf-encoded structure.
This issue affects:
- QR codes for channels created directly on the T-Deck via the MUI.
- QR codes for existing channels created or imported via the app in BLE Programming mode.
Example:
- Channel Name: TEST
- Channel PSK (as base64 string): ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890+/12344=
Generated link on T-Deck (invalid):
https://meshtastic.org/e/#ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890-_12344
Correct link (generated by the app, which properly encodes the full channel protobuf):
https://meshtastic.org/e/#CigSIAAQgxBRhyCSizDTj0EUk1FVl2Gddt-Oeu_PdPv9dt-OGgRURVNUEg0IATgDQAdIAVAbyAYB
Steps to Reproduce:
- On a T-Deck device running MUI firmware (tested on versions 2.7.2 and 2.7.3):
- Create a new channel directly on the device via the MUI or import/create a channel using the app in BLE Programming mode. Use a PSK that includes special characters like
/,+, and=(e.g., the example above). - Navigate to the channel settings in the MUI and generate/display the QR code for that channel.
- Create a new channel directly on the device via the MUI or import/create a channel using the app in BLE Programming mode. Use a PSK that includes special characters like
- On a different Meshtastic node/device, open the Meshtastic app (e.g., Android/iOS app).
- Attempt to scan the QR code displayed on the T-Deck using the app's QR code scanner.
Expected Behavior:
The QR code should contain a properly encoded link (base64url of the serialized ChannelSet protobuf, including the channel name, binary PSK, and other settings) and be successfully scanned by the app, allowing the channel to be added or configured on the other node.
Actual Behavior:
The QR code contains an invalid link that only includes a modified PSK string (with / → _, + → -, and = omitted), omitting the full protobuf structure. This causes the app to fail to recognize or scan the QR code, preventing the channel from being imported/added to the other node.
Relevant log output
- Lingua principale
- C
- Stelle
- 499
- Fork
- 125
- Merge medio
- 12h 6m
- PR unite (30g)
- 15
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di meshtastic/device-ui
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
meshtastic/device-ui#392 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
meshtastic/device-ui#283 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
meshtastic/device-ui#410 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
meshtastic/device-ui#403 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
meshtastic/device-ui#402 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di meshtastic/device-ui
Issue simili
-
native-cpu: -Wreturn-type in skainet_row_threads.c:150 (worker fn has no return)Forse già presa @Doomguy-BFG9000 l’ha presa oggi. Apertagood first issue size:xs skill:native
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
SKaiNET-developers/SKaiNET#1358 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
I/O internal correctness medium priority rt_lib
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
libsdl-org/SDL#16539 ·
I maintainer di solito rispondono entro 1 giorno
-
git-workflow task-4
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno