From: Sebastian Werner <sebastian@werner-productions.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Secure Gentoo
Date: Wed, 06 Mar 2002 19:53:20 +0100 [thread overview]
Message-ID: <2RM954X4Y43311VD8CFBUOUSB6LF42.3c8665a0@wp> (raw)
In-Reply-To: <1015436636.30680.24.camel@elysium.suxos.org>
This is great really great. I have not really much time to play with this. But I
could help you in parts of to do work. Contact me and we could do it.
I think it's enough to create acl's for the basesystem and some special
server apps. All these kde and gnome apps must not be installed on a real
server I think - so you need no acl's here.
Greetings
Sebastian
Am 06.03.2002 18:43:28, schrieb Joachim Blaabjerg <styx@SuxOS.org>:
>Hi again, people,
>
>If you don't have any further ideas/thoughts/objections/whatever, I'll
>finally start working on Secure Gentoo (or whatever the name is) now.
>I've had a few time problems lately, so I'm sorry I haven't got started
>earlier.
>
>What I'm going to do:
>* Make a profile with a small (minimal) set of apps, and slowly expand
>it as I get more packages done/patched.
>* Make a kernel patch, probably based on the Gentoo kernel, but with
>GrSecurity, kerneli, a few netfilter patches etc.
>* Patch packages with patches from the Owl GNU/*/Linux project (of which
>I am lucky to be a currently idling developer), and make ACLs for each
>app.
>
>My original intent was to use LIDS, but I've somewhat changed my mind.
>The ACL system in grsec has matured greatly lately, and I'm trying it
>out as we speak. Have any of you got any experiences or thoughts on this
>you want to share?
>
>I've got a few questions, too:
>Will the Gentoo kernel use Andrea Arcangeli's VM or Rik van Riel's (-aa
>or rmap)?
>How will this be done practically? I'm thinking in particular about the
>freeze, and the proposed unstable branch.
>How paranoid should it be? My first plan was to create ACLs for each and
>every binary and deny almost everything else, but that might be too
>paranoid for most people. What do you think? How about three security
>levels (no ACLs, normal ACLs and very strict ACls)?
>
>Any other thoughts and ideas will be greatly appreciated :)
>
>--
>Joachim Blaabjerg
>styx@SuxOS.org
>www.SuxOS.org
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
next prev parent reply other threads:[~2002-03-06 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 17:43 [gentoo-dev] Secure Gentoo Joachim Blaabjerg
2002-03-06 18:04 ` Daniel Robbins
2002-03-06 18:53 ` P.Gnodde
2002-03-06 21:24 ` Nic Desjardins
2002-03-06 20:50 ` Joachim Blaabjerg
2002-03-07 21:26 ` mbutcher
2002-03-06 18:53 ` Sebastian Werner [this message]
2002-03-08 11:12 ` Joachim Blaabjerg
2002-03-07 20:08 ` Karl Trygve Kalleberg
2002-03-08 11:11 ` Joachim Blaabjerg
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=2RM954X4Y43311VD8CFBUOUSB6LF42.3c8665a0@wp \
--to=sebastian@werner-productions.de \
--cc=gentoo-dev@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