[Bug 284994] Re: bluetooth-wizard unable to pair to fixed pin devices

tz thomas at mich.com
Mon Nov 24 15:05:41 GMT 2008


That sounds like a good idea provided:

1. Pincodes are specified to be as long as 16 digits.  If you are
going to bother with a random pin, it should be 8 digits by default if
security is not to be just a lesser joke.  Apple uses 8.  If you have
a PIN entry box, it should allow a max of 16 digits.

2. GTK Text areas (unless I've missed something) allow for non-numeric
entry.  The spinboxes are pure numeric so there is no way to do
00000000 v.s. 0000.  Something should validate or limit user input to
the 10 numeric digits.  This should be done before the patch goes into
the main codebase.

3. The format is good (later in the message):

If Pin is required:
(*) Enter PIN of RRRRRRRR on Device
( ) Device specifies PIN of [0000____________]

(radiobutton, not checkbox)

-----------------
On Mon, Nov 24, 2008 at 8:24 AM, spaetz <sebastian at sspaeth.de> wrote:
> CADE20 wrote:
>> I modified my patch, I've added a textbox for choosing any pincode.
>
> Please see the upstream dev discussion on how the bluez developer would
> solve the issue in a way that seems reasonable:
> http://thread.gmane.org/gmane.linux.bluez.kernel/717/focus=721
>
> Such a patch should be done according to that and submitted upstream, to
> solve this the correct way once and for all.
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
bluetooth-wizard unable to pair to fixed pin devices
https://bugs.launchpad.net/bugs/284994
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez-gnome in ubuntu.



More information about the Ubuntu-bluetooth mailing list