From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: <minipli@googlemail.com>, <herbert@gondor.apana.org.au>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net 0/4] xfrm_user info leaks
Date: Tue, 29 Aug 2017 06:43:45 +0200 [thread overview]
Message-ID: <20170829044345.GD3311@secunet.com> (raw)
In-Reply-To: <20170828.155232.1540318133719787999.davem@davemloft.net>
On Mon, Aug 28, 2017 at 03:52:32PM -0700, David Miller wrote:
> From: Mathias Krause <minipli@googlemail.com>
> Date: Sat, 26 Aug 2017 17:08:56 +0200
>
> > Hi David, Steffen,
> >
> > the following series fixes a few info leaks due to missing padding byte
> > initialization in the xfrm_user netlink interface.
> >
> > Please apply!
>
> Steffen please pick this up if you haven't already.
I had it already in the ipsec/testing branch, now merged into
ipsec/master.
Thanks everyone!
prev parent reply other threads:[~2017-08-29 4:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 15:08 [PATCH net 0/4] xfrm_user info leaks Mathias Krause
2017-08-26 15:08 ` [PATCH net 1/4] xfrm_user: fix info leak in copy_user_offload() Mathias Krause
2017-08-26 15:08 ` [PATCH net 2/4] xfrm_user: fix info leak in xfrm_notify_sa() Mathias Krause
2017-08-26 15:08 ` [PATCH net 3/4] xfrm_user: fix info leak in build_expire() Mathias Krause
2017-08-26 15:09 ` [PATCH net 4/4] xfrm_user: fix info leak in build_aevent() Mathias Krause
2017-08-26 15:58 ` [PATCH net 0/4] xfrm_user info leaks Joe Perches
2017-08-26 19:56 ` Mathias Krause
2017-08-28 22:52 ` David Miller
2017-08-29 4:43 ` Steffen Klassert [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=20170829044345.GD3311@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=minipli@googlemail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).