Comment 143 for bug 284994

I disagree Robie. The problem relates to the fact that the bluetooth GUI tool requires a PIN. Earlier in this thread, it was about that people couldn't choose a PIN, or use the standard 0000, 1234, 1111, etc. Then that was solved, but now there are devices such as my mouse that require NO PIN at all. The GUI doesn't allow for this case. It FORCES you to choose a PIN. As a user, I should NEVER have to drop to a command line and execute some cryptic commands or muck with "auth encrypt" or whatever that is. The GUI tool just needs to be smarter (or in this case, dumber) and let me enter NO PIN. In fact, it could even be another radio button like so:

( ) 0000
( ) 1111
( ) 1234
( ) custom PIN [_____]
( ) no pin required