/var/db/bthcid.keys
file and provides them as required when Bluetooth connections
need to be authenticated.
These keys are required for connections between remote devices and the specific controller (not the Operating System) and so for multi-boot systems where it may not always be possible to specify the same key across all OS's it can be better to have the Bluetooth controller provide the keys directly from its semi-permanent memory once devices are paired. btkey will read, write or clear keys in device memory or the key cache as required.
Note that without the bthcid(8) daemon running users will be unable to supply PINs, and Link Keys resulting from new pairings will not be stored. If no new pairings are expected and the keys are stored in the controller then bthcid(8) is not required.
The options are as follows:
Super-user privileges are required to read or write link keys.
Read key for mouse at ubt0 from file and write to device
btkey
-d
ubt0
-a
mouse
-rW
Write new key for keyboard at ubt0 to file
btkey
-d
ubt0
-a
keyboard
-k
92beda6cd8b8f66ebd2af270d55d70ec
-w
Clear key for phone at bt3c0 from file and device
btkey
-d
bt3c0
-a
phone
-cC
/var/db/bthcid.keys