public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: EXT-Somil.Asthana@nokia.com
Cc: d.mackie@ru.ac.za,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] Can you spoof/forge Bluetooth Devices/Address?
Date: Mon, 07 Jun 2004 23:01:48 +0200	[thread overview]
Message-ID: <1086642107.28514.21.camel@pegasus> (raw)
In-Reply-To: <E320A8529CF07E4C967ECC2F380B0CF90140382B@bsebe001.americas.nokia.com>

Hi Somil,

>   Looks like I am in minority here :(. Actually you are very correct there aren't any phone with PAN or UPnP (its in one of our TODO list). Further, Symbian 8.0 release will have a PAN stack anyway (it will be interesting to interface with Bluez PAN  stack, as there are some issues). So for the time being you can look for solutions like Distributed SDP database, tunneling for the RFCOMM channels. They look every exciting but requires lot of debugging/testing  based on my experience on developing/debugging l2cap broadcast utility (using Bluez util code) and I didn't do anything novel there. As far as I see maintaining /updating Distributed SDP database is no different from cache coherence problem (but I am nt expert so I shouldn't really say that but I thought about it :)).

if you think that there are BlueZ PAN vs. Symbian PAN problems, feel
free to send me a PAN enabled phone and I will check what happens on our
side. Maybe the BlueZ code is buggy. I hope not, but it may be possible.

The idea with distributed SDP and a L2CAP/RFCOMM tunnel is very old. I
know that this works, because I already used it to reverse engineer the
FBus over Bluetooth part of the Nokia Data Suite that way. I didn't used
IP as tunnel between the two piconet, because BlueZ is able to work with
more than one dongle (or expensive PCMCIA cards in my case) attached to
the same host. Some easy tricks if you can't buy yourself a protocol
analyzer ;)

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-06-07 21:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 20:27 [Bluez-users] Can you spoof/forge Bluetooth Devices/Address? EXT-Somil.Asthana
2004-06-07 21:01 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  6:29 Michael Schmidt
2004-06-07  0:26 EXT-Somil.Asthana
2004-06-07  8:11 ` Marcel Holtmann
2004-06-07 16:03   ` David Mackie
2004-06-06 23:24 EXT-Somil.Asthana
2004-06-06 23:55 ` Marcel Holtmann
2004-06-06 16:21 David Mackie
2004-06-06 16:50 ` Collin R. Mulliner
2004-06-06 21:10 ` Marcel Holtmann
2004-06-07  8:18 ` Xavier Garreau
2004-06-07  8:28   ` 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=1086642107.28514.21.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=EXT-Somil.Asthana@nokia.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=d.mackie@ru.ac.za \
    /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