From: Chris Wright <chrisw@osdl.org>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH} 2.6 and grsecurity
Date: Mon, 16 Feb 2004 18:45:35 -0800 [thread overview]
Message-ID: <20040216184535.D16277@build.pdx.osdl.net> (raw)
In-Reply-To: <200402170237.i1H2bb3r008280@turing-police.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Mon, Feb 16, 2004 at 09:37:36PM -0500
* Valdis.Kletnieks@vt.edu (Valdis.Kletnieks@vt.edu) wrote:
> OK.. I can do that easily enough - only reason I didn't was because that would
> force the inclusion of ip_randomid() and the corresponding call even when the
> feature wasn't selected, making it more intrusive (the 'else' clause is also the
> "when not configured at all" code - moving the whole if/then/else to another
> function was more intrusive, to my thinking..)
could be
#ifndef CONFIG_RANDID
#define ip_randomid(x) (x)
#else
int ip_randomid(int id)
{
if(security_enable...)
return random_one();
return id;
}
#endif
or somesuch, you get the idea.
> > > + * 3. All advertising materials mentioning features or use of this softwar
> e
> > > + * must display the following acknowledgement:
> > > + * This product includes software developed by Niels Provos.
> >
> > Advertsing clause...this is not GPL compatible.
>
> Thanks for spotting that. It's the same way in grsecurity's patch - do they
> have an issue as well? Or they OK because they're only doing a separately
> distributed patch?
I suspect yes, but, of course, IANAL ;-)
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-02-17 2:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 1:34 Valdis.Kletnieks
2004-02-17 2:15 ` Chris Wright
2004-02-17 2:37 ` Valdis.Kletnieks
2004-02-17 2:45 ` Chris Wright [this message]
2004-02-17 6:13 ` James Morris
2004-02-17 6:48 ` Valdis.Kletnieks
2004-02-17 14:23 ` Martin Waitz
2004-02-17 14:53 ` Valdis.Kletnieks
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=20040216184535.D16277@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®