All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Subject: Re: /proc woes
Date: Tue, 8 Oct 2002 21:29:18 +0200	[thread overview]
Message-ID: <20021008212917.A6663@lemuria.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0210081439380.25356-100000@raven>; from sds@tislabs.com on Tue, Oct 08, 2002 at 02:43:12PM -0400

On Tue, Oct 08, 2002 at 02:43:12PM -0400, Stephen Smalley wrote:
> > Rebooting the machine fixed it, so this may have happened during either
> > make relabel or make load (I installed a new policy today), though it's
> > still a mystery to me how and I'm one of the people who believe that a
> > reboot shouldn't be a valid solution. :)
> 
> I can't see any reason why a 'make relabel' or a 'make load' would yield
> this behavior.  'make relabel' only runs setfiles on mounted ext[23] or
> reiserfs filesystems to create or update the persistent label mappings.
> 'make load' doesn't relabel anything, although it might invalidate
> security contexts if you removed types (like proc_t), leaving existing
> objects in unlabeled_t (but not file_t).

Well, I *am* somewhat puzzled myself, but I've seen it happen. I will
experiment a little tomorrow afternoon to see if I can recreate it
(probably by replaying the bash history) and find out what caused this.


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

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

      reply	other threads:[~2002-10-08 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 14:32 /proc woes Tom
2002-10-08 14:40 ` Stephen Smalley
2002-10-08 15:11   ` Tom
2002-10-08 17:13     ` Russell Coker
2002-10-09 10:30       ` Tom
2002-10-08 18:43     ` Stephen Smalley
2002-10-08 19:29       ` Tom [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=20021008212917.A6663@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.