Files
paseo/docs
Mohamed Boudra e50482d4c2 Learn the relay security pin from the active client, whichever path made it
A strict pairing offer kept its minimum only until the relay upsert rebuilt the connection without it, and a pin learned by a client was persisted only when the controller had constructed that client itself. Probe clients adopted from pairing or startup never reported it, so a saved host that negotiated protected lost the pin on restart.

The offer's parsed connection is now stored as is. The controller reads the active client's negotiated floor when it reports connected and asks the store to pin the daemon identity; client constructors no longer carry a persistence callback.
2026-10-21 15:33:21 +02:00
..