From: David Miller <davem@davemloft.net>
To: jmorris@namei.org
Cc: netdev@vger.kernel.org, sds@tycho.nsa.gov, eparis@redhat.com,
kaber@trash.net, chrisw@sous-sol.org
Subject: Re: [PATCH][SECURITY] secmark: nul-terminate secdata
Date: Sun, 30 Jul 2006 20:47:03 -0700 (PDT) [thread overview]
Message-ID: <20060730.204703.78159806.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0607281649440.20690@d.namei>
From: James Morris <jmorris@namei.org>
Date: Fri, 28 Jul 2006 17:00:15 -0400 (EDT)
> The patch below fixes a problem in the iptables SECMARK target, where the
> user-supplied 'selctx' string may not be nul-terminated.
Applied, thanks James.
next prev parent reply other threads:[~2006-07-31 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 21:00 [PATCH][SECURITY] secmark: nul-terminate secdata James Morris
2006-07-29 1:19 ` Patrick McHardy
2006-07-31 3:47 ` David Miller [this message]
2006-08-02 18:28 ` Chris Wright
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=20060730.204703.78159806.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chrisw@sous-sol.org \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/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).