From: forrest whitcher <fw@fwsystems.com>
To: Ben Ritter <benritter@earthlink.net>
Cc: selinux@tycho.nsa.gov
Subject: Re: Mandrake and Slackware Distros
Date: Mon, 30 Dec 2002 06:17:29 -0500 [thread overview]
Message-ID: <20021230061729.16f6d5fa.fw@fwsystems.com> (raw)
In-Reply-To: <CF725BE6-1A0C-11D7-9B43-003065AE1370@earthlink.net>
I've been testing / using the selinux kernel on slackware-current (running
in a VMware vm) with good results for 3 months now, and have also now
installed lsm/selinux on a laptop.
I'll be installing a new server soon and will run on either slack or rh.
w/ selinux.
I haven't had time to put together my notes of what needs to be done on
slack. certainly you need to build / install PAM, if kerberos isn't
installed then the ssh build needs to be patched and I think there was a
problem with incude header files involving ncurses and a few other minor
issues, mostly predictable due to layout problems.
I've tried on more experimental linuxes and had very poor results however.
forrest
On Fri, 27 Dec 2002 18:33:55 -0800 (unchecked - local sync NTPstrat4)
Ben Ritter <benritter@earthlink.net> did inscribe thusly:
> Hey Group,
> I'm kinda new here, how secure are the current distributions of
> Mandrake and Slackware linux?
>
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2002-12-30 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 2:33 Mandrake and Slackware Distros Ben Ritter
2002-12-28 4:21 ` Russell Coker
2002-12-30 11:17 ` forrest whitcher [this message]
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=20021230061729.16f6d5fa.fw@fwsystems.com \
--to=fw@fwsystems.com \
--cc=benritter@earthlink.net \
--cc=selinux@tycho.nsa.gov \
/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.