Heya, If one didn't read the Bluetooth 2.1 specs, we could easily miss that particular point. Passkeys used for SSP need to have zeros prepended if they are less than 6 digits long. Added to the docs in the patch below, and will fix the bugs in gnome-bluetooth. Cheers
>From 86b5302feedd578256aea400b8f220515220885e Mon Sep 17 00:00:00 2001 From: Bastien Nocera <hadess@xxxxxxxxxx> Date: Wed, 25 May 2011 16:30:09 +0100 Subject: [PATCH] doc: Add mention of the 6-digit padding problem Passkeys used for Secure Simple pairing should always appear zero-padded in the end-user display, as per specification (5.4 ASSOCIATION MODELS in BLUETOOTH SPECIFICATION Version 2.1 + EDR [vol 1]) --- doc/agent-api.txt | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/doc/agent-api.txt b/doc/agent-api.txt index 0c84e1c..fca2875 100644 --- a/doc/agent-api.txt +++ b/doc/agent-api.txt @@ -63,6 +63,10 @@ Methods void Release() During the pairing process this method might be called multiple times to update the entered value. + Note that the passkey will always be a 6-digit number, + so the display should be zero-padded at the start if + the value contains less than 6 digits. + void RequestConfirmation(object device, uint32 passkey) This method gets called when the service daemon @@ -71,6 +75,10 @@ Methods void Release() To confirm the value it should return an empty reply or an error in case the passkey is invalid. + Note that the passkey will always be a 6-digit number, + so the display should be zero-padded at the start if + the value contains less than 6 digits. + Possible errors: org.bluez.Error.Rejected org.bluez.Error.Canceled -- 1.7.5.1
