Created attachment 1733 [details] Patch This patch adds basic support for SSH connections over Bluetooth RFCOMM sockets. It only adds the autoconf magic, along with support for correctly reporting the peer when sshd has been invoked with the '-i' argument from a Bluetooth dæmon working much like inetd, such as the one I have at http://david.woodhou.se/btserv.c Later patches will add the functionality from 'btserv.c' into sshd so that it can listen for itself, and will add support to the ssh client for making the connections directly; currently my testing uses 'ProxyCommand socat stdio SOCKET-CONNECT:31:3:x1ec1e4e21f000100'
I don't think we want this - it's pretty niche and can be achieved using a ProxyCommand on the client or wrapper around sshd in inetd mode at the server.
Actually this *was* using a ProxyCommand and wrapper (not inetd itself, of course, since that's for IP. The linked btserv.c does it). This patch was just the bare minimum to get sshd correctly handling the socket and reporting the source address. The potential benefit of merging the btserv part is that we get to standardise the UUID (the Bluetooth equivalent of the standard port 22) for SSH over Bluetooth service. But this was all 9 years ago and my use case for this (mini PC in the car running as a music server and pretending to be a CD changer) isn't even running any more. And if I reinstate it, 802.11 connectivity is somewhat more reliable these days so I don't *need* to rely on being able to connect to it over Bluetooth when it can't connect to the network :)
Close RESOLVED bugs with the release of openssh-8.0