All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose Vasconcellos <jose@vasmac.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Error: Authentication Failure
Date: Wed, 04 Oct 2006 08:13:46 -0400	[thread overview]
Message-ID: <4523A57A.4020709@vasmac.com> (raw)
In-Reply-To: <1159950383.1601.3.camel@localhost>

Marcel Holtmann wrote:
...
>>> It's pretty easy to reproduce. I've tried with two USB dongles
>>> (CSR & Broadcom) and different headsets. Connect a device
>>> on Linux, then take the device and dongle and connect on
>>> Windows; when you go back with both to Linux you get this
>>> problem.
>>>
>>> You are right that one can remove the bonding manually but
>>> this is not obvious to the uninitiated and it requires a manual
>>> step. Plus, the message presented to the application is
>>> typically "Record not found" if the first connection is an SDP
>>> lookup.
>>>
>>> Perhaps in security.c in utils/hcid, the routine conn_complete
>>> should delete the cached entry if there's an error.
>>>       
>
> this is not an option, because it will be a security risk. We have to
> keep the old key until we actually generated a new one or someone
> deleted the old one. The only think that is possible it too improve the
> error message.
>
> These are also known errors and you can even switch BlueZ into a pairing
> once mode. This is because device should implement a pairing mode. That
> means that will never accept a pairing if they are not in that mode. So
> if the link key is a wrong one, it simply rejects the connection instead
> of starting a new pairing process.
>
> Regards
>
> Marcel
>   
Hi Marcel,

I'm not familiar with the security issues; that is not my focus.
I game a suggestion based on a cursory look at the source code.
There is a problem here and it looks like the Windows
environment can cope with this but Bluez can't. Granted this
is not very common condition.

Jose


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-10-04 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03  3:45 [Bluez-devel] Error: Authentication Failure Jose Vasconcellos
2006-10-03 16:54 ` Claudio Takahasi
2006-10-03 17:48   ` Claudio Takahasi
2006-10-04  1:41     ` Jose Vasconcellos
2006-10-04  3:37       ` Mayank BATRA
2006-10-04  8:26       ` Marcel Holtmann
2006-10-04 12:13         ` Jose Vasconcellos [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4523A57A.4020709@vasmac.com \
    --to=jose@vasmac.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.