From: Marcel Holtmann <marcel@holtmann.org>
To: tpeyrin@cpe.fr
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] sniffing others devices - noob
Date: Thu, 08 Apr 2004 14:20:54 +0200 [thread overview]
Message-ID: <1081426854.2970.31.camel@pegasus> (raw)
In-Reply-To: <1081426638.407542ce468c7@webmail.cpe.fr>
Hi Thomas,
> well i've already read it ... but i thought that the link key was not
> transmitted in clear. The first data transmitted is in_rand the first random
> value. hcidump doesn't display data transmitted ??
you should read it again. The link key and also the pin code are never
transmitted in clear over the air.
hcidump displays all data on the HCI level. Use the -x switch to look
into some packets.
> if not, do you know a free software that can allow me to catch those data.
On lower levels than HCI you only get the information with a protocol
analyser.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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:[~2004-04-08 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 11:44 [Bluez-users] sniffing others devices - noob Thomas PEYRIN
2004-04-08 12:00 ` Marcel Holtmann
[not found] ` <1081425934.4075400e59f4f@webmail.cpe.fr>
2004-04-08 12:13 ` Marcel Holtmann
[not found] ` <1081426638.407542ce468c7@webmail.cpe.fr>
2004-04-08 12:20 ` Marcel Holtmann [this message]
[not found] ` <1081427623.407546a7165b8@webmail.cpe.fr>
2004-04-08 13:10 ` Marcel Holtmann
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=1081426854.2970.31.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=tpeyrin@cpe.fr \
/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