From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Russell Coker <russell@coker.com.au>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: cifs_t
Date: Wed, 7 Jul 2004 20:28:48 +0000 [thread overview]
Message-ID: <20040707202848.GC12112@lkcl.net> (raw)
In-Reply-To: <1089224292.1774.160.camel@moss-spartans.epoch.ncsc.mil>
On Wed, Jul 07, 2004 at 02:18:12PM -0400, Stephen Smalley wrote:
> On Mon, 2004-07-05 at 09:52, Russell Coker wrote:
> > typealias sambafs_t alias cifs_t;
> >
> > What is the benefit of the above?
> >
> > If we are going to make cifs_t the new name for what is currently sambafs_t
> > then surely the correct thing to do is to change the declaration of sambafs_t
> > to cifs_t and use the following typealias:
> >
> > typealias cifs_t alias sambafs_t;
>
> Looking at the CVS tree, it appears that it was changed from cifs_t to
> sambafs_t on 5/4/2004, as part of a merge of a policy diff from Fedora.
> cifs_t was retained as an alias for compatibility, IIRC.
i understand from russell that cifs_t (sambafs_t) is for client-side
access auditing (not from server-side stuff as i originally assumed).
... what happens when wine, which is in the process of implementing its
own [entire] smb client access method, due to license incompatibility
[and intransigence] of samba [team], provides an alternative
non-samba-based SMB access system?
... or is that something to worry about for another day, as-and-when?
l.
--
--
Information I post is with honesty, integrity, and the expectation that
you will take full responsibility if acting on the information contained,
and that, should you find it to be flawed or even mildly useful, you
will act with both honesty and integrity in return - and tell me.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
--
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.
next prev parent reply other threads:[~2004-07-08 4:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 13:52 cifs_t Russell Coker
2004-07-05 18:58 ` cifs_t Luke Kenneth Casson Leighton
2004-07-07 18:18 ` cifs_t Stephen Smalley
2004-07-07 20:28 ` Luke Kenneth Casson Leighton [this message]
2004-07-08 8:00 ` cifs_t 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=20040707202848.GC12112@lkcl.net \
--to=lkcl@lkcl.net \
--cc=russell@coker.com.au \
--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.