From: Marcel Holtmann <marcel@holtmann.org>
To: Vincenzo Ampolo <vincenzo.ampolo@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Stefano Zanero <zanero@elet.polimi.it>
Subject: Re: Bluetooth honeypot - hci socket that reads package problem -
Date: Mon, 20 Jul 2009 09:45:28 +0200 [thread overview]
Message-ID: <1248075928.4549.91.camel@violet> (raw)
In-Reply-To: <200907200938.35808.vincenzo.ampolo@gmail.com>
Hi Vincenzo,
> For my thesis, i'm trying to write a bluez based honeypot.
> The basic concept is to listen at the hci level and perform actions. (switch
> on sockets in rfcomm or l2cap channels or addresses to audit the data)
>
> I started studying the hcidump code and the hci socket. The main problem i'm
> having is that the hci socket which is created in this way
>
> sk = socket(AF_BLUETOOTH, SOCK_RAW, BTPROTO_HCI);
>
> does not "pop" the package from the bluez stack, it just reads but the package
> will continue to be processed by the stack. So if there is an attempt for a
> connection it will find a closed socket. Is there a way to "pop" the package
> from the stack, so i can read the destination channel or address of the
> package and turn on a socket on that specified channel or address and then
> "push" again the package into the stack?
>
> If it's not possible, the only way to set my bluetooth honeypot up is to open
> a socket for each rfcomm and l2cap channel and address and wait for data to
> audit.
what you are planning is to write a whole Bluetooth stack in userspace,
but wanna have the kernel do the hardware abstraction :)
You need to set the device into RAW mode. Otherwise the kernel will keep
processing the HCI packets.
Regards
Marcel
next prev parent reply other threads:[~2009-07-20 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 7:38 Bluetooth honeypot - hci socket that reads package problem - Vincenzo Ampolo
2009-07-20 7:45 ` Marcel Holtmann [this message]
2009-07-20 13:03 ` Vincenzo Ampolo
2009-07-20 13:09 ` 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=1248075928.4549.91.camel@violet \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vincenzo.ampolo@gmail.com \
--cc=zanero@elet.polimi.it \
/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