All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: boot loader
Date: Tue, 23 Apr 2002 07:40:55 +0200	[thread overview]
Message-ID: <20020423074055.B14880@lemuria.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0204221825010.5657-100000@raven>; from sds@tislabs.com on Mon, Apr 22, 2002 at 06:27:54PM -0400

On Mon, Apr 22, 2002 at 06:27:54PM -0400, Stephen Smalley wrote:
> There is one other potential issue.  If an administrator directly edits
> /etc/lilo.conf, it will revert to etc_t (and become inaccessible to lilo
> unless it is then relabeled by the administrator).  Is there any strong
> reason to maintain a separate type on this file?  It is problematic to
> keep it in a separate type from other /etc files, since it may be directly
> modified by the administrator and it doesn't live in its own separate
> subdirectory.

It may be more tricky even. I'm thinking about split administrator access 
here. Say you have one network and one system admin. Network admin needs 
to access stuff in /etc (such as interface configs, maybe some or all 
network daemons, depending on where authorities are split) while system 
admin needs access to other /etc files (cron and startup files, among 
others).


-- 
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.

  parent reply	other threads:[~2002-04-23  5:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20 12:37 boot loader Russell Coker
2002-04-20 15:24 ` Ivan Pulleyn
2002-04-20 18:14   ` Russell Coker
2002-04-22 11:48 ` Stephen Smalley
2002-04-22 19:58   ` Russell Coker
2002-04-22 20:39     ` Stephen Smalley
2002-04-22 22:08       ` Russell Coker
2002-04-22 22:27         ` Stephen Smalley
2002-04-22 22:45           ` Russell Coker
2002-04-23  5:43             ` Tom
2002-04-23 11:55               ` Russell Coker
2002-04-23 12:20                 ` Tom
2002-04-23 12:44                   ` Russell Coker
2002-04-23 15:36                     ` Tom
2002-04-23 16:50                       ` Russell Coker
2002-04-23 17:03                         ` Stephen Smalley
2002-04-23  5:40           ` Tom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-28 15:12 Thiago Farina
2015-04-28 21:49 ` Richard Weinberger
2015-04-28 23:44   ` Thiago Farina
2015-04-29  2:17     ` Ken Moffat
2015-04-29  8:28 ` Geert Uytterhoeven
2015-05-11 22:11 ` Pavel Machek
2015-05-12  0:17   ` Thiago Farina
2015-05-12 11:11     ` Enrico Weigelt, metux IT consult
2015-05-13  7:02       ` Pavel Machek
2015-05-13  7:53         ` Enrico Weigelt, metux IT consult
2015-05-13  7:56           ` Pavel Machek
2003-12-22  9:58 Executable delay James Bates
2003-12-22 11:59 ` Boot Loader Kevin A. Sapp
2003-12-22 13:08   ` Wolfgang Denk
2002-12-09  6:05 Erik Christiansen
2002-12-09  7:43 ` Wolfgang Denk
2002-12-10  7:54   ` Erik Christiansen
2002-04-22 12:43 boot loader Westerman, Mark
     [not found] <36E192B5.6C18381B@noaa.gov>
1999-03-07  1:04 ` Cort Dougan
1999-03-08 10:14   ` Gabriel Paubert
1999-03-08 19:33     ` Cort Dougan

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=20020423074055.B14880@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.