All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Antill <jantill@redhat.com>
To: Klaus Weidner <klaus@atsec.com>
Cc: Paul Moore <paul.moore@hp.com>, SE Linux <selinux@tycho.nsa.gov>,
	Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: Fedora Core 7 has frozen and Fedora 8 Development has started
Date: Tue, 22 May 2007 10:51:52 -0400	[thread overview]
Message-ID: <1179845512.23650.35.camel@code.and.org> (raw)
In-Reply-To: <20070521221304.GB11544@w-m-p.com>

[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]

On Mon, 2007-05-21 at 17:13 -0500, Klaus Weidner wrote:

> Would it make sense to make a distinction between end user modifiable
> types and admin types? For example, at first glance the following look as
> if they'd be most relevant for non-admin users:

 Right, the admin can use nautilus too :). Note that if a context is
viewed that doesn't match any of those translations the failure mode is
to just display the full context to the user, so I wanted to add all of
the types that any user would hit in at least ~/ and /etc.

> >        HACK_TYPE("cvs_data_t", _("Read and write from CVS daemon"));
> >        HACK_TYPE("public_content_rw_t",
> >                  _("Read and write from CIFS/ftp/http/nfs/rsync"));
> >        HACK_TYPE("public_content_t", _("Read from CIFS/ftp/http/nfs/rsync"));
> >        HACK_TYPE("samba_share_t", _("Shared via CIFS (samba)"));
> >        HACK_TYPE("staff_home_t", _("Staff user data"));
> >        HACK_TYPE("staff_home_dir_t", _("Staff user home directory"));
> >        HACK_TYPE("sysadm_home_t", _("Sysadmin user data"));
> >        HACK_TYPE("sysadm_home_dir_t", _("Sysadmin user home directory"));
> >        HACK_TYPE("tmp_t", _("Temporary data"));
> >        HACK_TYPE("user_tmp_t", _("User temporary data"));
> >        HACK_TYPE("user_home_t", _("User data"));
> >        HACK_TYPE("user_home_dir_t", _("User home directory"));
> >        HACK_TYPE("xen_image_t", _("Xen image"));
> 
> Maybe one way to do that would be to use a drop-down for the type that
> only contains the types that the user is actually permitted to change
> this object to?

 The above function _just_ does the translation from a type to "readable
message saying what the type is". This is not the list of entries that
is displayed to the user.
 The list is generated by always adding tmp_t, user_home_t, user_tmp_t
and then whatever is contained in selinux_customizable_types_path().
Then the current type for the file, and the matchpathcon type for the
file (with all the other values for the context taken from the current
context). That's not very pretty either, but it doesn't make me cringe
as much as the above :).

-- 
James Antill <jantill@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2007-05-22 14:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 20:59 Fedora Core 7 has frozen and Fedora 8 Development has started Daniel J Walsh
2007-05-21 19:08 ` Klaus Weidner
2007-05-21 19:15   ` Daniel J Walsh
2007-05-21 19:43     ` Paul Moore
2007-05-21 20:27       ` James Antill
2007-05-21 22:13         ` Klaus Weidner
2007-05-22  1:34           ` Paul Moore
2007-05-22 13:31           ` Joshua Brindle
2007-05-22 14:54             ` Todd Miller
2007-05-22 15:14               ` Joshua Brindle
2007-05-22 15:36                 ` Todd Miller
2007-05-22 16:00                   ` Joshua Brindle
2007-05-23 14:01                 ` Karl MacMillan
2007-05-22 14:51           ` James Antill [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=1179845512.23650.35.camel@code.and.org \
    --to=jantill@redhat.com \
    --cc=dwalsh@redhat.com \
    --cc=klaus@atsec.com \
    --cc=paul.moore@hp.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.