From: Jordi Jaen Pallares <jordijp@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Key exchange before pairing
Date: Wed, 29 Jun 2005 16:43:51 +0200 [thread overview]
Message-ID: <537e39c905062907433980aa7f@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
Hi @ll !
I would like to know if it is possible to perform a "peer key exchange"
prior to the pairing operation, in order to for example, have the peers
exchange some extra information about them and be able for example to
look-up different PINs for every different service / connection / device.
I have written a little program using rfcomm sockets (although I am planing
to change them to BNEP ones) which carries out the data exchange without
problems as long as the security manager is set to 'none'.
But I would like to be able to replace the normal pairing procedure with
this "key exchange between bluetooth peers" procedure:
* it is then possible to trigger (maybe via 'pin_helper' ?) a data exchange
between the two bluetooth sockets (using raw L2CAP sockets, for example)
while the devices are _not paired_ and while the security level is set at
least to authentication ?
* I tried to change the rfcomm "working" sockets program to L2CAP sockets,
but then I don´t know which Protocol Service MUX (psm) value I might have to
set for this sockets to have them connect successfully (the one from an
already existing service, one of the reserved values?!).
I tried different odd values greater than 1 for the psm (using htobs(psm))
and I get the following error message:
Cannot connect to socket: Connection refused (111)
I would really appreciate it if you could help me out or give me some advise
on these topics.
Best Regards,
Jordi
[-- Attachment #2: Type: text/html, Size: 1632 bytes --]
next reply other threads:[~2005-06-29 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 14:43 Jordi Jaen Pallares [this message]
2005-06-29 17:57 ` [Bluez-users] Key exchange before pairing Marcel Holtmann
2005-06-29 23:24 ` Jordi Jaen Pallares
2005-06-30 5:10 ` Marcel Holtmann
2005-07-01 5:28 ` Jordi Jaen Pallares
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=537e39c905062907433980aa7f@mail.gmail.com \
--to=jordijp@gmail.com \
--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 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.