From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] remote device identification
Date: Thu, 24 May 2007 12:08:33 +0200 [thread overview]
Message-ID: <1180001313.26519.22.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <57c68ddc0705240306s1c9fc345x860dc75b9955d6f@mail.gmail.com>
Hi,
> I recently came upon this white paper name as
> blueprinting (titled Remote Device Identification based on Bluetooth
> Fingerprinting Techniques) which presents a way of identifying remote
> device by using sdp discovery records.
>
> What this paper claims is that by using combination of first 3 bytes
> of bluetooth address and number obtained by multiplying service record
> handle and rfcomm channel of OBEX push services one can identify the
> brand or make of the device.
>
> I would like to know how reliable this method is , also can u suggest
> other techniques which can accomplish such thing.
it is not really reliable anymore. Too many vectors changed over the
last 2 years.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-05-24 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 10:06 [Bluez-users] remote device identification siddhant tewari
2007-05-24 10:08 ` Marcel Holtmann [this message]
2007-05-24 10:12 ` siddhant tewari
-- strict thread matches above, loose matches on Subject: below --
2007-02-06 22:28 Mikael Lindqvist
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=1180001313.26519.22.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--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