Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Buttonless boards have no way to reopen the pairing window once a phone is bonded

Aperta
  • Qualcosa non va?
#54 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
embedded-iot, security

Direzione di ricerca

Read docs/ble.md and the changes discussed in #9, #18, and #46 to understand the current pairing-window behavior. The issue proposes several possible recovery paths, including a new system command, a physical action, authenticated pairing, or app guidance, but does not choose one. Done means a buttonless board can add, replace, or remove phones without erasing flash while preventing strangers from opening the pairing window.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Part of #9. Follow-up to #18 / #46.

Problem

  • Since #46, a board without a pairing button (e.g. the WiCAN) opens the pairing window at boot only while no phone is bonded. Once a phone is bonded, nothing can open it again.
  • RemovePairedPhone / ClearPairedPhones also need an open window, so a buttonless board can't manage its phones at all after first setup.
  • If the owner's phone loses its bond (forgotten in Android's Bluetooth settings, app reinstalled, new phone), it's locked out. With the window closed the device advertises without its name or service UUID, so the app doesn't even find it. Tested on a WiCAN with #46: the phone reconnects as a known identity but never re-encrypts, and no bond is stored.
  • The only recovery today is erasing the flash over USB.

Ideas

  • A deliberate action that opens the window:
    • a system command from a bonded phone (needs a new message in contracts);
    • a physical action, such as unplugging and replugging the device a set number of times within a short time.
  • Use authenticated pairing (passkey or numeric comparison) where the hardware allows it, e.g. a code shown in the app and confirmed with a pattern on the device's LED. This was an idea in #18 and goes away when it closes.
  • In the app, when a previously paired device isn't found, explain the recovery instead of scanning forever (mobile-app side, like OpenCarControls/mobile-app#42 for the reverse case).
  • Update docs/ble.md, which currently says "such a board is reset by erasing its flash".

Done when
The owner of a buttonless board can add, replace or remove a phone without erasing the flash, and a stranger near the car still can't open the window.

Lingua principale
Rust
Stelle
1
Fork
0
Merge medio
10h 56m
PR unite (30g)
15

Preparare l'ambiente

Apri in Codespaces

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

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenCarControls/firmware

Tutte le issue di OpenCarControls/firmware

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.