public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Ritscher,  Fraunhofer-Institut SIT" <matthias.ritscher@sit.fraunhofer.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Encryption Key Length Negotiation & Link Key Type
Date: Thu, 28 Dec 2006 11:02:18 +0100	[thread overview]
Message-ID: <4593962A.6070303@sit.fraunhofer.de> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 1082 bytes --]

Hi Bluez-List,

1)
I´m trying to get any information about the Encryption Key Negotiation 
Process of paired Bluetooth devices (Laptop with Bluez-stack and a 
Handheld Device). Using hcidump I could not receive any information 
about this exchange which corresponds to that negotiation. I sniffed 
communication exchange during pairing and communication transmission. 
Encryption at the host is enabled in the hcid.conf file and can be seen 
using "hcitool con".
I´m interested in the length of the negotiated Encryption key Kc. Is 
there any way to retrieve its length (or value) in the Bluez-stack ?

2)
The second issue I´m focussing in this request is the question: Is there 
is a possibility in the Bluez-stack to "simulate" devices with light 
memory or computing power ;-) ? This means, is there a possibility that 
the Bluez-stack will use a Local Unit Key as Link Key proposal. I´m 
interested, since the counterpart (Handheld Device) is supposed by 
specification to accept Combination Keys as Link Keys only, and I want 
to test it.

Thanks for your attention,
Matthias


[-- Attachment #1.1.2: matthias.ritscher.vcf --]
[-- Type: text/x-vcard, Size: 372 bytes --]

begin:vcard
fn:Matthias  Ritscher
n:Ritscher;Matthias 
org:Fraunhofer-Institut Sichere Informationstechnologie;Sichere mobile Systeme
adr;quoted-printable;dom:;;Rheinstra=C3=9Fe 75;Darmstadt;;64295
email;internet:matthias.ritscher@sit.fraunhofer.de
tel;work:+49 (0) 6151 / 869 - 313
tel;fax:+49 (0) 6151 / 869 - 224
url:http://www.sit.fraunhofer.de
version:2.1
end:vcard


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3764 bytes --]

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

-------------------------------------------------------------------------
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

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

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

                 reply	other threads:[~2006-12-28 10:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4593962A.6070303@sit.fraunhofer.de \
    --to=matthias.ritscher@sit.fraunhofer.de \
    --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