Linux bluetooth development
 help / color / mirror / Atom feed
From: Jordi Jaen Pallares <jordijp@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Key exchange before pairing
Date: Fri, 1 Jul 2005 07:28:49 +0200	[thread overview]
Message-ID: <537e39c905063022282fdbb14f@mail.gmail.com> (raw)
In-Reply-To: <1120108243.15397.138.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]

Hi Marcel,

first of all, thank you for your comments :-)

2005/6/30, Marcel Holtmann <marcel@holtmann.org>:
> 
> Hi Jordi,
> 
> > I´d like to generate the PIN based on the shared key derived from a
> > Diffie Hellman exchange between the bluetooth peers.
> 
> if you wanna use Diffie Hellman, for what reason do you want to use the 
> pairing and encryption of Bluetooth then.


I would like to use the pairing and encryption of bluetooth as usual, and 
use only the Diffie-Hellman exchange to generate a "stronger" PIN for the 
pairing. 

> Is it possible to trigger this exchange at pairing time using my own 
> > 'pin_helper' program ?
> 
> To exchange data you need a connection first. This means you can only do
> this in security mode 1 and 2. The PIN helper can't be used for any of
> these task except entering a PIN.


But then, is there any other way for the peers to exchange previous 
communication attributes than using the SDP protocol ?

Is it possible to exchange information by previously registering a new 
service (with a fixed PSM) and then negociate the parameters directly using 
L2CAP sockets ?

Regards,

Jordi


Regards
> 
> Marcel
> 
> ------------------------------------------------------- 
> SF.Net <http://SF.Net> email is sponsored by: Discover Easy Linux 
> Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to 
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&opclick<http://ads.osdn.com/?ad_idt77&alloc_id%16492&opclick>
> _______________________________________________
> Bluez-users mailing list 
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users 
>

[-- Attachment #2: Type: text/html, Size: 2596 bytes --]

      reply	other threads:[~2005-07-01  5:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 14:43 [Bluez-users] Key exchange before pairing Jordi Jaen Pallares
2005-06-29 17:57 ` 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 [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=537e39c905063022282fdbb14f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox