All of lore.kernel.org
 help / color / mirror / Atom feed
From: Debian User <rogelio@evoworks.evoserve.com>
To: Stephen Smalley <sds@tislabs.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: selinux cramfs
Date: Fri, 21 Jun 2002 20:51:38 +0800	[thread overview]
Message-ID: <3D13215A.6060109@evoworks.evoserve.com> (raw)
In-Reply-To: Pine.GSO.4.33.0206210844000.12888-100000@raven

Great! I was planning to hack away already.

Stephen Smalley wrote:

>On Fri, 21 Jun 2002, Stephen Smalley wrote:
>
>>You might be able to handle cramfs to some degree using the new
>>genfs_contexts configuration, which is a generalization of devfs_contexts.
>>That isn't in the current release, but will be in the next one.
>>
>
>I just tried using genfs_contexts to specify a context for cramfs and
>then mounting a cramfs image, and it appears to work correctly.  So this
>will hopefully be addressed by the next public release.
>
>--
>Stephen D. Smalley, NAI Labs
>ssmalley@nai.com
>
>




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

  reply	other threads:[~2002-06-21 12:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21  4:48 selinux cramfs Debian User
2002-06-21 11:00 ` Russell Coker
2002-06-21 11:49   ` Debian User
2002-06-21 12:25     ` Stephen Smalley
2002-06-21 12:45       ` Stephen Smalley
2002-06-21 12:51         ` Debian User [this message]
2002-06-21 12:54         ` Russell Coker
2002-06-21 13:08           ` Debian User
2002-06-21 12:28     ` Russell Coker

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=3D13215A.6060109@evoworks.evoserve.com \
    --to=rogelio@evoworks.evoserve.com \
    --cc=sds@tislabs.com \
    --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.