From: "David S. Miller" <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@oss.sgi.com
Subject: Re: [IPSEC] Verify key payload in verify_one_algo
Date: Thu, 19 May 2005 12:40:59 -0700 (PDT) [thread overview]
Message-ID: <20050519.124059.85410159.davem@davemloft.net> (raw)
In-Reply-To: <20050519021505.GA20703@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 19 May 2005 12:15:05 +1000
> We need to verify that the payload contains enough data so that
> attach_one_algo can copy alg_key_len bits from the payload.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Also applied, thanks again.
I gather from these two patches that once you found the
first problem you went around auditing alg_key_len usage
and these were the only two bugs you spotted. Right?
next prev parent reply other threads:[~2005-05-19 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 2:03 [IPSEC] Fixed alg_key_len usage in attach_one_algo Herbert Xu
2005-05-19 2:15 ` [IPSEC] Verify key payload in verify_one_algo Herbert Xu
2005-05-19 19:40 ` David S. Miller [this message]
2005-05-19 21:34 ` Herbert Xu
2005-05-19 19:40 ` [IPSEC] Fixed alg_key_len usage in attach_one_algo David S. Miller
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=20050519.124059.85410159.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
/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