From: Tom <tom@lemuria.org>
To: SELinux@tycho.nsa.gov
Subject: Re: db conflict ?
Date: Fri, 12 Apr 2002 16:50:34 +0200 [thread overview]
Message-ID: <20020412165034.A29953@lemuria.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0204121019570.21729-100000@raven>; from sds@tislabs.com on Fri, Apr 12, 2002 at 10:21:48AM -0400
On Fri, Apr 12, 2002 at 10:21:48AM -0400, Stephen Smalley wrote:
> > One thing that I noticed during this setup was that the patched login
> > and ssh tools do not appear to work if they run on a non-lsm kernel.
> > While this is probably the right thing to do security-wise, it also
> > means that keeping a non-SELinux kernel as "rescue system" on-disk
> > doesn't help a thing.
>
> I can't speak for the Debian selinux packages, but the upstream SELinux
> modified daemons and utilities run fine on non-SELinux kernels and non-LSM
> kernels. They simply fall back to the ordinary processing in that case.
I didn't spot any differences in the diff file, and I've just looked
through it trying to find my remote login bug.
Anyway, I dig both ways of doing it, and I can always keep a rescue CD
near, I'm just used to having a 2nd kernel around.
--
http://web.lemuria.org/pubkey.html
pub 1024D/D88D35A6 2001-11-14 Tom Vogt <tom@lemuria.org>
Key fingerprint = 276B B7BB E4D8 FCCE DB8F F965 310B 811A D88D 35A6
--
You have received this message because you are subscribed to the selinux 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.
next prev parent reply other threads:[~2002-04-12 14:50 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 10:23 db conflict ? Tom
2002-04-12 12:05 ` Russell Coker
2002-04-12 13:01 ` Tom
2002-04-12 14:07 ` Russell Coker
2002-04-12 14:40 ` Stephen Smalley
2002-04-12 15:15 ` Russell Coker
2002-04-12 19:03 ` [patch] " Stephen Smalley
2002-04-12 13:09 ` Stephen Smalley
2002-04-12 13:27 ` Russell Coker
2002-04-12 13:06 ` Stephen Smalley
2002-04-12 13:58 ` Russell Coker
2002-04-12 14:07 ` Stephen Smalley
2002-04-12 14:38 ` Russell Coker
2002-04-12 14:48 ` Stephen Smalley
2002-04-12 15:12 ` Russell Coker
2002-04-12 17:01 ` Howard Holm
2002-04-12 17:09 ` Russell Coker
2002-04-12 17:13 ` Stephen Smalley
2002-04-12 14:17 ` Tom
2002-04-12 14:21 ` Stephen Smalley
2002-04-12 14:34 ` Russell Coker
2002-04-12 14:50 ` Tom [this message]
2002-04-12 15:01 ` Tom
2002-04-12 15:11 ` Stephen Smalley
2002-04-12 15:15 ` Tom
2002-04-12 15:29 ` Tom
2002-04-12 16:35 ` Stephen Smalley
2002-04-12 16:50 ` Tom
2002-04-12 17:04 ` Stephen Smalley
2002-04-12 17:40 ` Tom
2002-04-12 17:49 ` Stephen Smalley
2002-04-12 16:33 ` Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2002-04-12 17:26 Westerman, Mark
2002-04-12 17:29 ` Stephen Smalley
2002-04-12 17:37 Westerman, Mark
2002-04-12 18:03 ` Russell Coker
2002-04-12 19:17 ` Stephen Smalley
2002-04-12 20:11 ` Russell Coker
2002-04-12 20:25 ` Howard Holm
2002-04-12 21:01 ` Russell Coker
2002-04-15 14:44 ` Howard Holm
2002-04-12 20:18 ` Howard Holm
2002-04-15 16:08 ` Dale Amon
2002-04-18 14:54 ` Stephen Smalley
2002-04-18 15:42 ` Russell Coker
2002-04-19 20:20 ` Stephen Smalley
2002-04-12 17:45 Westerman, Mark
2002-04-12 18:12 ` Stephen Smalley
2002-04-12 18:13 Westerman, Mark
2002-04-12 19:42 ` Russell Coker
2002-04-12 20:33 Westerman, Mark
2002-04-15 14:40 ` Howard Holm
2002-04-15 15:16 Westerman, Mark
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=20020412165034.A29953@lemuria.org \
--to=tom@lemuria.org \
--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.