From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] auto pairing between client & server
Date: Tue, 26 Apr 2005 15:39:20 +0200 [thread overview]
Message-ID: <1114522760.10706.280.camel@pegasus> (raw)
In-Reply-To: <426E1B8F.8030901@gmx.ch>
Hi Marco,
> > What I want is to avoid the pin popup for certain bluetooth devices
> > (know specific BD_ADDR). When those allowed devices connect to my
> > device, then I will try to provide "silently" the PIN (no popups) and
> > the pairing should be done from there. If other device which BD_ADDR
> > does not belong to the list of addresses that my device has, it should
> > not be rejected.
>
> I don't think this is possible because you don't know the remote BD_ADDR
> until the device has connected to your device. And if it has already
> connected, it's too late for bluteooth based autentication/encryption. So
> you might implement an own authentication/encryption algorithm for your
> purpose.
you already have an temporary underlaying ACL link, because otherwise it
is impossible to request the authentication and encryption. All pin code
and link key oriented events tell you the remote BD_ADDR. So this is
actually no problem to realize.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-04-26 13:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 20:06 [Bluez-users] auto pairing between client & server N. I.
2005-04-22 21:38 ` Marcel Holtmann
2005-04-24 16:17 ` Fredy P
2005-04-25 14:26 ` N. I.
2005-04-26 10:07 ` N. I.
2005-04-26 11:28 ` Marcel Holtmann
2005-04-23 21:31 ` Marco Trudel
2005-04-25 14:29 ` N. I.
2005-04-25 14:38 ` Marco Trudel
2005-04-26 10:02 ` N. I.
2005-04-26 10:44 ` Marco Trudel
2005-04-26 13:39 ` Marcel Holtmann [this message]
2005-04-26 11:31 ` Marcel Holtmann
2005-04-26 17:37 ` Marco Trudel
2005-04-26 17:46 ` Marcel Holtmann
2005-04-26 18:36 ` Marco Trudel
2005-04-26 19:04 ` Marcel Holtmann
2005-04-26 22:31 ` N. I.
2005-04-27 8:44 ` Marco Trudel
2005-04-27 8:50 ` Marcel Holtmann
2005-04-27 8:54 ` Marco Trudel
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=1114522760.10706.280.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@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