From: Marcel Holtmann <marcel@holtmann.org>
To: Jessica Huang <jessieh@MIT.EDU>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bd_addr question
Date: Wed, 10 Mar 2004 01:23:47 +0100 [thread overview]
Message-ID: <1078878227.30990.17.camel@pegasus> (raw)
In-Reply-To: <5.2.1.1.2.20040309190444.02e6e250@po14.mit.edu>
Hi Jessica,
> Sorry, I worded it poorly. I'm a graduate student researching privacy
> issues related to Bluetooth, which I'm pretty new to. I'm trying to work a
> way around the fact that each device address is unique therefore
> trackable. I was wondering if I were to buy a Bluetooth transmitter and
> build my own device, can I change the bd_addr that is stored by the chip's
> manufacturer? Which layer/module is in charge of reading that unique
> bd_addr? I hope that makes more sense!
the Bluetooth SIG is working on something that is called Anonymity Mode
and this should be present in Bluetooth 1.2, but it got removed from the
final specification. So actually devices are trackable. And there is no
default way of changing the BD_ADDR, but some manufacturers provides
vendor specific HCI commands to change the Bluetooth address.
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-03-10 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 20:12 [Bluez-devel] bd_addr question Jessica Huang
2004-03-09 21:24 ` Marcel Holtmann
[not found] ` <5.2.1.1.2.20040309190444.02e6e250@po14.mit.edu>
2004-03-10 0:23 ` Marcel Holtmann [this message]
2004-03-10 9:46 ` Collin R. Mulliner
-- strict thread matches above, loose matches on Subject: below --
2004-03-10 7:45 Michael Schmidt
2004-03-10 11:22 ` Steven Singer
2004-03-10 16:04 Mark RISON
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=1078878227.30990.17.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jessieh@MIT.EDU \
/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