mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dennis, Jim" <jdennis@snapserver.com>
To: "'Chris Wright'" <chris@wirex.com>,
	"Dennis, Jim" <jdennis@snapserver.com>
Cc: "'Jeff Garzik'" <jgarzik@mandrakesoft.com>,
	Andreas Dilger <adilger@turbolabs.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: crypto (was Re: Congrats Marcelo,)
Date: Tue, 26 Feb 2002 16:42:12 -0800	[thread overview]
Message-ID: <2D0AFEFEE711D611923E009027D39F2B153ADA@cdserv.meridian-data.com> (raw)


 


> * Dennis, Jim (jdennis@snapserver.com) wrote:
> <snip>
>> As for LIDS, grsecurity, etc: I suspect it will be a cold day in hell
>> before Linus includes any of those into the mainstream.  I think it is
>> sufficient that he's willing to accommodate the LSM (security module)
>> to provide a common interface to all of the competing kernel hardening
>> packages.
> <snip>

> You may interested to know, LIDS has been ported to LSM, which is kept
> up-to-date for stable 2.4 releases, and (for those with bitkeeper) all
> 2.5-pres/stable.

> cheers,
> -chris

 Yes, I had read that.  Do you know of any effort to consolidate the 
 crypto libs in LIDS, patch-int, and FreeS/WAN KLIPS?  I'd like to think 
 that they can be maintained more efficiently and result in lower overhead
 and integration effort if the core crypto algorithms are consolidated
 among those three.

 (I remember someone found three? or four? different implementations of the
 same checksum code in the mainstream kernel a couple of years ago; I hope
 that's been fixed long since).

 (Any flames about my armchair coaching and pointed suggestions that I
 get in there and help with this are welcome --- off the list! I won't take 
 offense, I just don't want to burden everyone else's mailbox with that).


             reply	other threads:[~2002-02-27  0:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27  0:42 Dennis, Jim [this message]
2002-02-27  1:02 ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2002-02-26 23:18 Dennis, Jim
2002-02-27  0:24 ` Chris Wright
2002-02-26 20:38 Congrats Marcelo, Dennis, Jim
2002-02-26 21:06 ` Andreas Dilger
2002-02-26 21:15   ` crypto (was Re: Congrats Marcelo,) Jeff Garzik
2002-02-26 22:33     ` Rik van Riel
2002-02-27 21:15       ` Michael H. Warfield
2002-02-27 21:57         ` Rik van Riel
2002-02-27 22:29           ` Michael H. Warfield
2002-02-27 23:06             ` Rik van Riel
2002-02-26 21:35   ` Robert Love
2002-02-26 21:40     ` arjan
2002-02-26 21:47       ` Robert Love
2002-02-24 23:51         ` Daniel Phillips
2002-02-28 22:32           ` Bill Davidsen
2002-03-01  9:50             ` Francois Romieu
2002-02-27  9:41     ` Francois Romieu

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=2D0AFEFEE711D611923E009027D39F2B153ADA@cdserv.meridian-data.com \
    --to=jdennis@snapserver.com \
    --cc=adilger@turbolabs.com \
    --cc=chris@wirex.com \
    --cc=jgarzik@mandrakesoft.com \
    --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®