From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux List <SELinux@tycho.nsa.gov>
Subject: Re: Desktop integration
Date: Mon, 30 Jan 2006 16:46:34 -0500 [thread overview]
Message-ID: <43DE893A.7030203@cornell.edu> (raw)
In-Reply-To: <43DE6578.9050302@redhat.com>
>>
>> The read interface will be easy (hopefully), but the write interface
>> is not clear. I think we want to aim for user-friendly selinux. For
>> categories, one possibility is to enumerate the translation strings
>> from setrans.conf, and have checkboxes for each that the user can
>> click (I like this idea). Another way to deal with this is a text
>> box, where we can enter translated or untranslated categories and/or
>> ranges.
> seobject.py currently does this, but of course it is written in python.
>
> It basically does a getcon on the process and then takes it MLSRange
> potion and translates it into reachable contexts
>
> s0-s0:c1.c5 = s0. s0:c1, s0:c2, s0:c3, s0:c4, s0:c5.
> It then attempts to translate each one of these to show the user which
> categories he can create files in.
You're right, I'm not making any sense.. was confused, thinking of a
different issue.
Should we add a utility function in libselinux that does this kind of
expand/translate processing?
--
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:[~2006-01-30 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 19:00 Desktop integration Ivan Gyurdiev
2006-01-30 19:14 ` Daniel J Walsh
2006-01-30 21:46 ` Ivan Gyurdiev [this message]
2006-02-01 13:08 ` Thomas Bleher
2006-02-01 14:00 ` Joshua Brindle
2006-02-28 5:57 ` Ivan Gyurdiev
2006-02-28 11:14 ` Daniel J Walsh
2006-02-28 16:40 ` Ivan Gyurdiev
2006-03-06 17:14 ` Daniel J Walsh
2006-03-06 21:58 ` Erich Schubert
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=43DE893A.7030203@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.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.