public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] kernel no longer in hardened-development overlay?
Date: Mon, 19 Apr 2010 18:16:23 +0100	[thread overview]
Message-ID: <4BCC8FE7.8050606@wildgooses.com> (raw)
In-Reply-To: <4BCC8AA3.4030506@pcdesk.net>

On 19/04/2010 17:53, Joseph C. Lininger wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hey folks,
> Has anyone else noticed that the entire hardened-sources package has
> vanished from the hardened-development overlay? I know it's a
> development overlay and all, but I figured I should mention it because
> it's just gone. All versions. It struck me as a bit odd. Any reason for
> this?
>    


I guess others will disagree, but I have never been a huge fan of the 
kernel ebuilds.  I'm just not clear what they buy you over downloading 
and compiling your own?  I think there are a few extra patches in the 
case of gentoo-sources, but that seems to be about it?


If you don't yet have an alternative in place then my choice is for the 
vserver+grsec patches that you can grab from the linux-vserver.org site 
and this gives you a very easy way to setup chroot style jails with 
lightweight virtualisation, plus all the grsec patches.  If you just 
want Pax then it's a fast moving target and you are best to grab and 
patch your own kernel anyway, and don't forget to keep an archive of pax 
patches used since they don't archive them on the site (annoying if you 
are trying to diff the diff or whatever)


I realise everyone has different needs, but perhaps try pulling your own 
kernel down and applying your own patches - I think it's about easier to 
maintain in most cases?

Good luck

Ed W



  reply	other threads:[~2010-04-19 18:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 16:53 [gentoo-hardened] kernel no longer in hardened-development overlay? Joseph C. Lininger
2010-04-19 17:16 ` Ed W [this message]
2010-04-19 18:31   ` Michael Orlitzky
2010-04-19 19:37     ` Mike Edenfield
2010-04-19 23:02       ` Ed W
2010-04-19 19:45     ` David Sommerseth
2010-04-19 22:27       ` [gentoo-hardened] " Kerin Millar
2010-04-19 23:15     ` [gentoo-hardened] " Ed W
2010-04-20  5:14       ` Kai Dietrich
2010-04-20 11:57         ` Darknight
2010-04-20 13:34           ` Ed W
2010-04-20 13:46             ` Pavel Labushev
2010-04-19 17:46 ` [gentoo-hardened] " Kerin Millar
2010-04-19 20:12   ` Guillaume Castagnino
2010-04-19 22:56     ` Ed W
2010-04-19 23:05 ` [gentoo-hardened] " Mansour Moufid
2010-04-19 23:24   ` Ed W
2010-04-19 23:43     ` Mansour Moufid
2010-04-20 12:36       ` [gentoo-hardened] " Kerin Millar
2010-04-20 15:36         ` David Sommerseth
2010-04-19 23:35   ` [gentoo-hardened] " klondike
2010-04-20  0:00     ` Anthony G Basile
2010-04-20  5:08       ` Tóth Attila

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=4BCC8FE7.8050606@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=gentoo-hardened@lists.gentoo.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