Hi Stale,

> Working on my Master's I want to be able to delete, write and read the
> link keys associated with a paired device. I found the functions
>
> int hci_read_stored_link_key(int dd, bdaddr_t *bdaddr, uint8_t all,
> int to)
> int hci_write_stored_link_key(int dd, bdaddr_t *bdaddr, uint8_t *key,
> int to)
> int hci_delete_stored_link_key(int dd, bdaddr_t *bdaddr, uint8_t all,
> int to)
>
> in hci.c and tried to use the delete-function. It seems to work, as
> the function call returns 0, indicating that no problems occured.
> However, the link key still appears
> in /var/libs/bluetooth/BD_ADDR/linkkeys, and a following
> authentication is still successfull.
> Hcidump reports this:
> < HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
>     bdaddr 00:09:DD:60:02:45 all 0
> > HCI Event: Command Complete (0x0e) plen 4
>     Delete Stored Link Key (0x03|0x0012) ncmd 1
>     status 0x11 deleted 2525
>     Error: Unsupported Feature or Parameter Value
>
> I guess it might be the value of parameter "all". I didn't know what
> it is, so I tried with 0 and 1 (apperently not correct). Anyone knows
> what this parameter of type uint8_t is for? I thought it might be like
> a "boolean" variable, instructing deletion of ALL the associated link
> keys. Am I far off?
>
> Another thing, about the hci_read_stored_link_key function. Is the key
> returned as an int-value or by some other means? I'm a bit confused
> about this matter..

all these functions deal with the link keys stored on the chip. The
default operation of BlueZ is not to store these link keys on the
Bluetooth chip itself. Have a look at the D-Bus API for BlueZ. The
methods ListBondings() and RemoveBonding() give you what you actually
need.

Regards

Marcel