From: John Haxby <john.haxby@oracle.com>
To: John Haxby <john.haxby@oracle.com>
Cc: netfilter-devel@vger.kernel.org, prarit@redhat.com
Subject: Re: [PATCH 0/2] Security improvements for xt_SYSRQ
Date: Fri, 24 Jun 2011 14:30:17 +0100 [thread overview]
Message-ID: <4E049169.9050805@oracle.com> (raw)
In-Reply-To: <cover.1308920081.git.john.haxby@oracle.com>
On 24/06/11 14:14, John Haxby wrote:
> These two patches are something I promised a long time ago and never
> actually got around to.
> [snip]
I'd like to ask, again, if we can include these upstream.
Last time I asked, Patrick McHardy not unreasonably suggested that
rather than being part of iptables (xtables) this would be better as a
standalone module. This seemed like a good idea: putting the sysrq
handler in an encapsulation socket gets it running in BH context so that
it even works when the machine is mostly wedged and you can still use
iptables for filtering to protect the destination address and port.
This worked beautifully until I tried to extend it to cover IPv6: IPv6
doesn't have an encapsulation socket (and probably shouldn't have). I
really don't want to provide an IPv4-only solution: that won't even work
today in some environments and it will certainly look rather lame before
long.
So can we have xt_SYSRQ upstream please? Pretty please? :-)
jch
next prev parent reply other threads:[~2011-06-24 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 13:14 [PATCH 0/2] Security improvements for xt_SYSRQ John Haxby
2011-06-24 13:14 ` [PATCH 1/2] Use %pI4/%pI6c instead of NIPQUAD_FMT/NIP6_FMT and make IPv6 work John Haxby
2011-06-24 21:40 ` Jan Engelhardt
2011-06-24 13:14 ` [PATCH 2/2] Improve security for xt_SYSRQ John Haxby
2011-06-24 22:04 ` Jan Engelhardt
2011-06-24 13:30 ` John Haxby [this message]
2011-06-24 14:08 ` [PATCH 0/2] Security improvements " Jan Engelhardt
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=4E049169.9050805@oracle.com \
--to=john.haxby@oracle.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=prarit@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.