From: Shaun Savage <savages@pcez.com>
To: SELinux@tycho.nsa.gov
Cc: Stephen Smalley <sds@tislabs.com>
Subject: Re: /etc/security/default_context vs. /etc/security/default_contexts
Date: Wed, 16 Jan 2002 08:17:10 -0800 [thread overview]
Message-ID: <3C45A786.8010009@pcez.com> (raw)
In-Reply-To: Pine.GSO.4.33.0201160934050.7787-100000@raven
What is it format of the /etc/security/default_contexts? It would be
easy to convert the utils to the new get_user_sids, but the format of
the file for setting the default would need to be defined.
Ideas?
Shaun
>The new libsecure functions and the /etc/security/default_contexts file
>doesn't address the issue of a generic user. It merely eliminates the
>need to maintain per-user entries in default_context and cron_context.
>There is still the problem of maintaining policy/users. As Mark Westerman
>suggested (and I agreed), this can be addressed through the definition of
>a generic user and some minor modifications to the libsecure functions to
>use this as the default, as long as you do not need to distinguish among
>such users in the policy. If you want to maintain distinct role sets for
>these users, then you will need to update policy/users in some manner.
>
>
--
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.
prev parent reply other threads:[~2002-01-16 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 15:47 /etc/security/default_context vs. /etc/security/default_contexts Charles Levert
2002-01-07 16:33 ` Stephen Smalley
2002-01-15 21:55 ` Shaun Savage
2002-01-16 14:37 ` Stephen Smalley
2002-01-16 16:17 ` Shaun Savage [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=3C45A786.8010009@pcez.com \
--to=savages@pcez.com \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@tislabs.com \
/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.