From: Pierre BETOUIN <info16@unsigned.ath.cx>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Bug in l2cap.c
Date: Wed, 18 Jan 2006 19:16:03 +0100 [thread overview]
Message-ID: <1137608163.3070.26.camel@lapt41p> (raw)
In-Reply-To: <1137606864.7000.22.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
Hi Marcel,
Le mercredi 18 janvier 2006 à 18:54 +0100, Marcel Holtmann a écrit :
> Hi Pierre,
>
> > Currently pentesting several bluetooth devices, I found a bug in hcidump
> > (tested version : 1.29).
>
> you know that hcidump is a testing/development utility? It is basically
> not supposed to be fully robust against malicious packets.
True, one more reason to correct this then, I agree with you ;)
> Feel free to provide a patch and not an exploit.
The patch is (nearly) in my previous mail : check it, I gave you the short piece
of code concerned, should not give you headache fixing it.
> Regards
>
> Marcel
Regards,
Pierre
--
Pierre BETOUIN
info16@unsigned.ath.cx
http://securitech.homeunix.org
GPG Key : 0x94D9CB23
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-01-18 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 17:47 [Bluez-devel] Bug in l2cap.c Pierre BETOUIN
2006-01-18 17:54 ` Marcel Holtmann
2006-01-18 18:16 ` Pierre BETOUIN [this message]
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=1137608163.3070.26.camel@lapt41p \
--to=info16@unsigned.ath.cx \
--cc=bluez-devel@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