From: Mayank BATRA <mayank.batra@st.com>
To: "'BlueZ development'" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Error: Authentication Failure
Date: Wed, 4 Oct 2006 09:07:09 +0530 [thread overview]
Message-ID: <001801c6e766$64596b20$9d0cc70a@dlh.st.com> (raw)
In-Reply-To: <4523113E.4000608@vasmac.com>
Hi Jose,
> Perhaps in security.c in utils/hcid, the routine conn_complete
> should delete the cached entry if there's an error.
In case you are planning to implement a patch to solve this problem,
remember that the Bluetooth Spec mentions something called "Repeated
Attempts". So, in case authentication/pairing fails, you can initiate
another authentication/pairing only after a certain amount of time. If you
try it before this time, the authentication/pairing would fail again. And
this time keeps on increasing exponentially with each failure.
Best Regards,
Mayank
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-10-04 3:37 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 [this message]
2006-10-04 8:26 ` Marcel Holtmann
2006-10-04 12:13 ` Jose Vasconcellos
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='001801c6e766$64596b20$9d0cc70a@dlh.st.com' \
--to=mayank.batra@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox