New pairing database

Goal is to write individual pairings (bonds) to separate file and have a more flexible file format. Currently all pairings (bonds) are stored in a single file (pairings.bin).

Goal is to store each pairing (bond) in a separate file in a pairings/ directory, named pairingN.bin (with N being 1,2,3,...). Each file stores a list of TLVs and has the version of the file format as first byte.

What I still want to implement:

• Remove ble.txt and mac.txt and use card10.cfg instead.

In the future I'd like to be able to read the other device's name after pairing and write that into the file so the user has an idea which device is represented by that pairing.

changed milestone to %v1.16

added 3 commits

• 0078707a - feat(bondings): Write each bond to a separate file
• 66314cc0 - fix(bondings): Bring API more in line with upstream
• 96d845f8 - change(ble): Use card10.cfg instead of ble.txt and mac.txt

Compare with previous version

added 1 commit

• 5ee8bfc7 - change(ble): Use card10.cfg instead of ble.txt and mac.txt

Compare with previous version

Looks good to me! Thanks for keeping our codebase clean.

However, I'm only a bot - so a human will still have to approve this request.

changed the description

changed the description

A future MR might introduce:

• Better handling of what happens when all three slots are used and the user wants to pair another device.
• Deleting ble.txt, mac.txt and pairings.bin on startup.

unmarked as a Work In Progress

added 4 commits

• 6d7635d9 - feat(bondings): Write each bond to a separate file
• 93234db7 - fix(bondings): Bring API more in line with upstream
• 3e24328f - fix(ble): Generate new ECC keys after pairing
• 747803cc - change(ble): Use card10.cfg instead of ble.txt and mac.txt

Compare with previous version

Looks good to me! Thanks for keeping our codebase clean.

However, I'm only a bot - so a human will still have to approve this request.

resolved all threads

approved this merge request