How to configure aioble (pairing)

[brianreinhold]

I am trying to work with the aioble library and am having problems with pairing. I have a device that sends a security request and it appears that the library automatically handles this request by invoking pairing. However, from a sniff I noted the bonding flag is set to 'no bonding' which means it does not store long term keys. This response is unacceptable to many medical devices which often set up pairing/bonding in one connection waiting to send any measurements in a second paired/bonded connection so only encryption is needed.

I need to be able to configure the system to set the bonding flag, and if the library does not support the storage of long term keys that means the application must, therefore the application will need to know when a security request is received and it will need access to the LTKs for storage such that encryption can be invoked on a reconnect. Access to the LTKs (and IRKs) will be needed in all pairing operations, be it as a result of a security request or an insufficient authentication error.

At this stage the desire is for the client application only to pair if the peripheral requests it (security request or insufficient authentication). This approach means the non Bluetooth-savvy user does not need to know if the sensor device is pairable or not.

I guess a bigger question is to what degree pairing/bonding is supported in aioble.

1. Is it even possible to change the pairing options during a security request (override library response) so the application pairs? In other words, how do I get notified of a security request?
2. Is it possible for the application to get access to the LTKs and IRKs?