From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Possible security vulnerability in hcid when calling pin helper
Date: Fri, 05 Aug 2005 13:12:14 +0200 [thread overview]
Message-ID: <1123240334.8331.112.camel@pegasus> (raw)
In-Reply-To: <42F34840.4070503@csr.com>
Hi Steven,
> >> I just stumbled upon a bug in hcid that can possibly be used as a
> >> security vulnerability: ...
> > thanks for catching this problem. Do you have a fix for it?
>
> On behalf of everyone at Unplugfest with whom you've been doing security
> testing, I'd just like to say, using my best impression of Nelson Muntz
> from The Simpsons, "Ha Ha!".
>
> :-)
what should I say? Sh* happens. I am still afraid of that day when I
have to hack into BlueZ. And this day will come ;)
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-08-05 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 3:09 [Bluez-devel] Possible security vulnerability in hcid when calling pin helper Henryk Plötz
2005-08-05 3:16 ` Marcel Holtmann
2005-08-05 4:39 ` Henryk Plötz
2005-08-05 8:39 ` Marcel Holtmann
2005-08-05 11:06 ` Steven Singer
2005-08-05 11:12 ` Marcel Holtmann [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=1123240334.8331.112.camel@pegasus \
--to=marcel@holtmann.org \
--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