From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] monitor: Validate HCI event/command parameter length when parsing
Date: Sun, 2 Mar 2014 18:39:34 +0200 [thread overview]
Message-ID: <20140302163934.GA398@localhost.P-661HNU-F1> (raw)
In-Reply-To: <1393701808-27186-1-git-send-email-anderson.lizardo@openbossa.org>
Hi Lizardo,
On Sat, Mar 01, 2014, Anderson Lizardo wrote:
> Print an error message if the parameter length for HCI commands/events
> does not match the actual remaining packet size.
>
> This mainly avoids using garbage bytes when parsing corrupted packets.
> The check was inspired on those used when parsing SCO/ACL packets.
> ---
> monitor/packet.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
Applied. Thanks.
Johan
prev parent reply other threads:[~2014-03-02 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 19:23 [PATCH BlueZ] monitor: Validate HCI event/command parameter length when parsing Anderson Lizardo
2014-03-02 16:39 ` Johan Hedberg [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=20140302163934.GA398@localhost.P-661HNU-F1 \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
/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