All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim McCullough <jim.mccullough@gmail.com>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
	Nigel Kukard <nkukard@lbsd.net>,
	linux-hotplug-devel@lists.sourceforge.net,
	SELinux <selinux@tycho.nsa.gov>,
	"Fedora SELinux support list for users & developers."
	<fedora-selinux-list@redhat.com>,
	harald@redhat.com, Bill Nottingham <notting@redhat.com>
Subject: Re: [idea] udev + selinux
Date: Tue, 31 Aug 2004 21:18:05 +0000	[thread overview]
Message-ID: <ae023b6004083114183fafe6da@mail.gmail.com> (raw)
In-Reply-To: <20040831200210.GH4375@lkcl.net>

This should be of great assistance with two home projects currently
and  1 work project due to the filesystem types.  I am still working
through size issues and further locking down the images.

Project 1 = SE Linux image for Netgear MR314 Wireless Lan Router
Project 2 = SE Linux image for Cisco 2501 Router
Project 3 = Debian Sarge Server build on SGI Octane with reiserfs (
Work for Network Management Server )

Thanks,
Jim McCullough

On Tue, 31 Aug 2004 21:02:10 +0100, Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> On Tue, Aug 31, 2004 at 03:26:43PM -0400, Stephen Smalley wrote:
> > On Tue, 2004-08-31 at 15:18, Luke Kenneth Casson Leighton wrote:
> > >  i think we need the input of more experienced people than us to
> > >  say why these associate things are needed.
> >
> > It provides control over the set of files that can live in a given
> > filesystem, based on their security types (equivalence classes).  As you
> > are now creating device types in a different filesystem type, further
> > allow rules are needed to allow that association.
> >
> > >  a correct implementation of the
> > >  hacked-together-relaxed-fscontext-hooks.c-patch results in an atomic
> > >  operation (mount with a new context which would otherwise need to be
> > >  achieved with two commands: mount followed by restorecon)
> >
> > The more important issue is that fscontext= lets you set the superblock
> > security context, not just the root directory context.  restorecon can't
> > do that.
>  
>  ah.
> 
>  thanks for clarifying, steven.
> 
>  l.
> 
> 
> 
> --
> 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.
> 


-- 
Jim McCullough


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id\x10808&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jim McCullough <jim.mccullough@gmail.com>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
	Nigel Kukard <nkukard@lbsd.net>,
	linux-hotplug-devel@lists.sourceforge.net,
	SELinux <selinux@tycho.nsa.gov>,
	"Fedora SELinux support list for users & developers."
	<fedora-selinux-list@redhat.com>,
	harald@redhat.com, Bill Nottingham <notting@redhat.com>
Subject: Re: [idea] udev + selinux
Date: Tue, 31 Aug 2004 17:18:05 -0400	[thread overview]
Message-ID: <ae023b6004083114183fafe6da@mail.gmail.com> (raw)
In-Reply-To: <20040831200210.GH4375@lkcl.net>

This should be of great assistance with two home projects currently
and  1 work project due to the filesystem types.  I am still working
through size issues and further locking down the images.

Project 1 = SE Linux image for Netgear MR314 Wireless Lan Router
Project 2 = SE Linux image for Cisco 2501 Router
Project 3 = Debian Sarge Server build on SGI Octane with reiserfs (
Work for Network Management Server )

Thanks,
Jim McCullough

On Tue, 31 Aug 2004 21:02:10 +0100, Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> On Tue, Aug 31, 2004 at 03:26:43PM -0400, Stephen Smalley wrote:
> > On Tue, 2004-08-31 at 15:18, Luke Kenneth Casson Leighton wrote:
> > >  i think we need the input of more experienced people than us to
> > >  say why these associate things are needed.
> >
> > It provides control over the set of files that can live in a given
> > filesystem, based on their security types (equivalence classes).  As you
> > are now creating device types in a different filesystem type, further
> > allow rules are needed to allow that association.
> >
> > >  a correct implementation of the
> > >  hacked-together-relaxed-fscontext-hooks.c-patch results in an atomic
> > >  operation (mount with a new context which would otherwise need to be
> > >  achieved with two commands: mount followed by restorecon)
> >
> > The more important issue is that fscontext= lets you set the superblock
> > security context, not just the root directory context.  restorecon can't
> > do that.
>  
>  ah.
> 
>  thanks for clarifying, steven.
> 
>  l.
> 
> 
> 
> --
> 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.
> 


-- 
Jim McCullough

--
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:[~2004-08-31 21:18 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 17:37 [idea] udev + selinux Nigel Kukard
2004-08-30 17:37 ` Nigel Kukard
2004-08-30 20:31 ` Luke Kenneth Casson Leighton
2004-08-30 20:31   ` Luke Kenneth Casson Leighton
2004-08-31  5:02   ` Nigel Kukard
2004-08-31  5:02     ` Nigel Kukard
2004-08-31  9:49     ` Luke Kenneth Casson Leighton
2004-08-31  9:49       ` Luke Kenneth Casson Leighton
2004-08-31 10:27       ` Nigel Kukard
2004-08-31 10:27         ` Nigel Kukard
2004-08-31 12:46         ` Luke Kenneth Casson Leighton
2004-08-31 12:46           ` Luke Kenneth Casson Leighton
2004-08-31 11:26       ` Luke Kenneth Casson Leighton
2004-08-31 11:26         ` Luke Kenneth Casson Leighton
2004-08-31 16:07 ` Luke Kenneth Casson Leighton
2004-08-31 16:07   ` Luke Kenneth Casson Leighton
2004-08-31 16:46   ` Nigel Kukard
2004-08-31 16:46     ` Nigel Kukard
2004-08-31 19:18     ` Luke Kenneth Casson Leighton
2004-08-31 19:18       ` Luke Kenneth Casson Leighton
2004-08-31 19:26       ` Stephen Smalley
2004-08-31 19:26         ` Stephen Smalley
2004-08-31 20:02         ` Luke Kenneth Casson Leighton
2004-08-31 20:02           ` Luke Kenneth Casson Leighton
2004-08-31 21:18           ` Jim McCullough [this message]
2004-08-31 21:18             ` Jim McCullough
2004-08-31 23:26             ` Luke Kenneth Casson Leighton
2004-08-31 23:26               ` Luke Kenneth Casson Leighton
2004-08-31 22:44       ` [OT] SELinux vs. other systems [was Re: [idea] udev + selinux] Linas Vepstas
2004-09-01 14:23         ` Richard Troth
2004-09-01 14:23           ` Richard Troth
2004-09-01 14:29         ` Colin Walters
2004-09-01 17:25         ` Linas Vepstas
2004-09-02 16:10           ` Stephen Smalley
2004-09-02 16:10             ` Stephen Smalley
2004-09-02 17:29             ` Lomac questions [was Re: [OT] SELinux vs. other systems] Linas Vepstas
2004-09-02 17:29               ` Linas Vepstas
2004-09-02 20:05               ` Luke Kenneth Casson Leighton
2004-09-02 20:05                 ` Luke Kenneth Casson Leighton
2004-09-02 12:15         ` [OT] SELinux vs. other systems [was Re: [idea] udev + selinux] Russell Coker
2004-09-02 17:07           ` Linas Vepstas
2004-09-04  8:49             ` Russell Coker
2004-09-02 17:19           ` Luke Kenneth Casson Leighton

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=ae023b6004083114183fafe6da@mail.gmail.com \
    --to=jim.mccullough@gmail.com \
    --cc=fedora-selinux-list@redhat.com \
    --cc=harald@redhat.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=lkcl@lkcl.net \
    --cc=nkukard@lbsd.net \
    --cc=notting@redhat.com \
    --cc=sds@epoch.ncsc.mil \
    --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.