Hello, I'm preparing a bluetooth "access point" using BlueZ 5.47, so that for example mobile phones can connect to it, and further use PAN profile (which is not part of this question). So far it works well, just using the JustWorks pairing method. I'd like to secure this a little bit, not allowing anyone to pair, rather to request passkey (let's say hardcoded string) before accepting pairing requested by a client mobile phone. After searching through documentation and much googling, I don't see any hints how to achieve this. I found some information about pairing agents in BlueZ5, both in bluetoothctl and custom (programming them seems complicated but viable and I cannot use simple-agent since I don't have python on my machine), but all the usecases seem to target on BlueZ being the client, who initiates pairing, and the agent takes care of inputting passkey required by the other side - which is the opposite of what I need. How to configure BlueZ5 to require passkey from any incomming pairing requests? Thanks very much for your answers! Libor -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
