public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "bsd user" <oldmoonster@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bt-sco problem
Date: Mon, 14 Jan 2008 23:48:00 +0800	[thread overview]
Message-ID: <359782e70801140748u338cdeeatb7cd24acfe1e5237@mail.gmail.com> (raw)
In-Reply-To: <20080114152829.GD6064@localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 484 bytes --]

Hi, experts,

I have a question about link level security as below:
When there are 2 Bluetooth keyboard both connected with the same 1 Laptop's
Bluetooth controller, and enabled link layer data encryption function, both
use the same PIN do the authentication, will the encryption key be the same
for both links in data stream? If they are different, then, host
controller's baseband need to maintain the 2 keys for the 2 links in the
flying, right?

Thanks very much for your answer!

[-- Attachment #1.2: Type: text/html, Size: 513 bytes --]

[-- Attachment #2: Type: text/plain, Size: 278 bytes --]

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-01-14 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 15:28 [Bluez-devel] bt-sco problem Marco Zavagno
2008-01-14 15:48 ` bsd user [this message]
2008-01-14 17:30 ` Brad Midgley

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=359782e70801140748u338cdeeatb7cd24acfe1e5237@mail.gmail.com \
    --to=oldmoonster@gmail.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