All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Haxby <john.haxby@oracle.com>
To: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] More secure SYSRQ for xtables-addons
Date: Fri, 12 Dec 2008 08:38:39 +0000	[thread overview]
Message-ID: <4942230F.2000106@oracle.com> (raw)
In-Reply-To: <4935747C.5090207@oracle.com>

John Haxby wrote:
> Hello All,
>
> This is a patch to the SYSRQ xtables-addon that is, I believe, secure 
> enough to use in moderately untrustworthy environments.
>
> This is an updated version of the patch to address comments previously 
> received.   The main change, prompted by Patrick McHardy's question, 
> is to allow the hash algorithm to be changed at module load time.  
> Other than that I've clarified the '\n' password termination and 
> updated the man page to include using -m limit, the configurable hash 
> algorithm and made it a little that you can send multiple request keys.

I don't know if I'm being overly anxious or impatient, but is there 
anything more I need to do for this updated patch?

jch

  reply	other threads:[~2008-12-12  8:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 12:28 [PATCH] More secure SYSRQ for xtables-addons John Haxby
2008-12-01 19:34 ` Jan Engelhardt
2008-12-01 22:02   ` John Haxby
2008-12-01 22:37     ` Jan Engelhardt
2008-12-01 22:40     ` sg_set_page not usable for .bss? Jan Engelhardt
2008-12-02  0:10       ` David Miller
2008-12-02  0:13         ` Jan Engelhardt
2008-12-02  0:14           ` David Miller
2008-12-02  1:41             ` Jan Engelhardt
2008-12-02  6:55               ` David Miller
2008-12-02  1:39 ` [PATCH] More secure SYSRQ for xtables-addons Patrick McHardy
2008-12-02  1:53   ` Jan Engelhardt
2008-12-02  9:43   ` John Haxby
2008-12-02 17:46 ` John Haxby
2008-12-12  8:38   ` John Haxby [this message]
2008-12-13 22:14     ` Jan Engelhardt
2008-12-15 12:09       ` 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=4942230F.2000106@oracle.com \
    --to=john.haxby@oracle.com \
    --cc=netfilter-devel@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 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.