From: Vincenzo Ampolo <vincenzo.ampolo@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Stefano Zanero <zanero@elet.polimi.it>
Subject: Bluetooth honeypot - hci socket that reads package problem -
Date: Mon, 20 Jul 2009 09:38:32 +0200 [thread overview]
Message-ID: <200907200938.35808.vincenzo.ampolo@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
Hi,
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.
Thanks.
--
Vincenzo Ampolo
http://goshawknest.wordpress.com/
http://vincenzo-ampolo.net
GnuPG Key:
http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search=0x9BF47CA71E506DE9
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-07-20 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 7:38 Vincenzo Ampolo [this message]
2009-07-20 7:45 ` Bluetooth honeypot - hci socket that reads package problem - Marcel Holtmann
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=200907200938.35808.vincenzo.ampolo@gmail.com \
--to=vincenzo.ampolo@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--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