Comment 1 Andre Klapper 2008-07-31 15:57:33 UTC

Hi Tony, is this still an issue with Diablo? Can you please tell us an exact
modell of Navman that you tried with?
And can you please provide a **step-by-step explanation** how to reproduce
this? It makes it much easier for the bugsquad and for developers to reproduce.

Thanks a lot in advance!

Comment 2 Andre Klapper 2009-01-14 23:04:38 UTC

Closing this bug report as no further information has been provided. Please
feel free to reopen this bug if you can provide the information asked for/if
you can still reproduce this. Thanks!

Additionl information has been requested.

You cant pair a bluetooth devise that uses words as a password. Only numbers
are allowed and all letters are "greyed out".

An example: Navman bluetooth gps device has a password of "NAVMAN" the tablet
will not allow these letters to be input. I know the usual convention is to use
numbers only but it would be so simple to allow words too.

Further info:

Item: Navman gps unit (model GPS4400)

Diablo: Yes still a problem.

Events: 
go to bluetooth on tablet
click devices
click "new"
when Navman found click on device and click "ok"
Then asked to pair
put curser in password box which brings up onscreen keyboads.
keyboard appears with all but numbers disabled and unable to input letters.

As I have said before the password is "navman" but the tablet keyboard will
only allow the input of numbers.

Comment 5 Andre Klapper 2009-01-15 02:08:38 UTC

A few notes to myself for reference:

Quoting from NB#16732:
"The dialog is currently using NUMERIC input mode which disables entering
characters. I think Bluetooth standard itself doesn't prevent using any
characters. Reason that we are using only numbers is that most phones (=
gateway devices) allow only entering numbers to this request."

And the Fremantle Bluetooth UI Spec, Table "Layout for Pair with device dialog"
says that the passcode field "accepts only numerical characters."

Comment 6 Andre Klapper 2009-01-30 11:26:00 UTC

Forwarding an internal comment:
"This Navman GPS 4400 device really seems to have an unusual default passcode,
but are there any others that do?
I don't think we should specifically support an odd device that was released
over five years ago."

So do you know of any other devices with the same problem?

Bluetooth 2.0+EDR Core
(http://www.bluetooth.com/NR/rdonlyres/1F6469BA-6AE7-42B6-B5A1-65148B9DB238/840/Core_v210_EDR.zip
vol4 p186-187) specifies alphanumeric (UTF-8, with a couple of restrictions)
passkeys up to 16 characters long, but also adds:

> For compatibility with devices with numeric keypads fixed PINs shall be com-
> posed of only decimal digits, and variable PINS may be composed of only dec-
> imal digits.

So strictly speaking it looks like (if the Navman passkey is fixed) the GPS4400
device is implementing the spec incorrectly (I'm reading "shall" as "MUST" and
"may" as "MAY" in the RFC2129 sense).

However, it would be a good idea to support alphanumeric passkeys for security
reasons, when pairing with another device that supports variable passkeys. 
Since the 2.0 spec was published a passive eavesdropping attack on the pairing
process was discovered
(http://www.eng.tau.ac.il/~yash/shaked-wool-mobisys05/index.html) and the
Bluetooth SIG now recommends using an 8-character alphanumeric passkey as the
minimum
(http://bluetooth.com/Bluetooth/Press/SIG/Bluetooth_SIG_Response_to_Recent_Analysis_of_Pairing_and_Security.htm).

Comment 8 Neil MacLeod 2009-02-15 01:25:57 UTC

(In reply to comment #7)
> So strictly speaking it looks like (if the Navman passkey is fixed) the GPS4400
> device is implementing the spec incorrectly (I'm reading "shall" as "MUST" and
> "may" as "MAY" in the RFC2129 sense).
> 

While you are most probably correct that the GPS4400 is implementing the
fixed-PIN spec incorrectly and Navman should have used a decimal-only PIN,
Nokia should not have restricted PIN entry to numbers only when a full
alphanumeric keypad (virtual or hardware) is available. The reasoning for doing
so seems to be based on the erroneous assumption that Nokia tablets would only
be connecting to phone/gateway devices - this simply isn't the case, and never
has been.

Not supporting alphanumeric PIN entry is clearly in breach of the Bluetooth
2.0+EDR Core spec (whoever commented against NB#16732 is therefore misinformed)
and the Fremantle Bluetooth UI specification (and bug NB#16732!) must be
updated accordingly.

Comment 9 Andre Klapper 2009-02-16 13:32:08 UTC

This has been FIXED for Fremantle.

Comment 10 Andre Klapper 2009-04-28 15:34:45 UTC

Setting Target Milestone to Fremantle SDK beta.

The dialog still defaults to numeric input mode, but letters can be entered
with fn or the virtual keyboard.  I was able to pair an N900 and a PC
successfully using an alphanumeric passcode.