From: Ben Hutchings <ben@decadent.org.uk>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
alexandre <alexandre@cmu.edu>
Subject: Re: [PATCH] reglib: Validate all structure and array lengths
Date: Fri, 19 Jul 2013 01:46:08 +0100 [thread overview]
Message-ID: <1374194768.15633.32.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <CAB=NE6Vz_3d9Vz62dNTWocT3MTqvG4Ez+MZc0w-w8KBgkaapxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
On Tue, 2013-07-16 at 18:31 -0700, Luis R. Rodriguez wrote:
> On Sun, Jun 30, 2013 at 4:49 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > Add checks that:
> > - Signature length does not exceed the file length (this was already
> > checked, but did not account for signature lengths greater than 2 GB)
> > - Database length is long enough for all structures we expect in it
> > - Array length calculations will not overflow
> >
> > To keep these checks simple, change the types of array length and index
> > variables to unsigned int (must be at least 32-bit, matching the file
> > format) and the types of byte-length variables to size_t.
> >
> > Alexandre Rebert <alexandre@cmu.edu> reported and provided a test case
> > for the signature length issue; the others I found by inspection.
> >
> > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
>
> Thanks! Despite the fact you didn't resend for a wider review and I
> would have preferred this split up into a few patches this has been
> sitting on wireless-regdb for a while, so after my review I just
> applied and pushed. Thanks again!
Sorry about that - I was meaning to re-send but it never quite got to
the top of my to-do list.
Ben.
--
Ben Hutchings
Humans are not rational beings; they are rationalising beings.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-07-19 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1372636171.5155.56.camel@deadeye.wl.decadent.org.uk>
2013-07-17 1:31 ` [PATCH] reglib: Validate all structure and array lengths Luis R. Rodriguez
2013-07-19 0:46 ` Ben Hutchings [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=1374194768.15633.32.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=alexandre@cmu.edu \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=wireless-regdb@lists.infradead.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