On Tue, 2025-06-03 at 11:38 -0400, Luiz Augusto von Dentz wrote: > Perhaps it is possible to write the link keys directly via cable but > then we need the OOB data, etc, to generate the keys which in my > opinion it just extra work that doesn't really add anything if just > works, or autopair, is used. In my experimental PoC I just generated a random 128-bit string and used it as the link key for both sides (placed into `LinkKey=' in BlueZ's `/info' and sent to DualSense over USB), which showed to be working perfectly. > Is it not seamless right now? Doesn't it use 'just works'/autopair? It is kind of seamless, but you still have to accept the pairing manually (e.g. be discoverable and with an active agent). In terms of security I'd say this behavior is indeed preferable (otherwise one could spoof the VID:PID and zero-click bond with the host), but it still requires two separate confirmations. If we could generate a static key, place it to both devices BUT at the same time mark the device as unconfirmed/untrusted/etc. locally, so that it is still going to trigger one and only one interactive pairing confirmation, that'd be the intended design at least in my view. Another possible way would be to automatically accept the first, dummy pairing request that doesn't bear a link key yet -- so no security risk there, but still more seamless experience for the user. -- Egor Vorontsov <sdoregor@xxxxxxxx>
