All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>
Subject: Desktop Integration Take 2
Date: Tue, 28 Feb 2006 16:01:56 -0500	[thread overview]
Message-ID: <4404BA44.8000503@cornell.edu> (raw)

Okay, after discussing various obstacles, I think it's time to come up 
with a new plan for integrating selinux w/ nautilus.
How about the following:

- Have a file controlled by libsetrans which maps customizable types to 
(unicode?) translated strings
- Have a file controlled by libsetrans which maps mls ranges to 
(unicode?) translated strings
     (setrans.conf)

- Require the mappings above to be 1:1.

- Have two functions (with better names):
get_customizable_types_by_user()
get_mls_labels_by_user()

The first takes a [Unix] user, and returns the translated labels of all 
customizable types accessible { relabelto } from that user.
The second takes a [Unix] user, and returns the translated labels of all 
mls ranges accessible from that user, [ only the labeled ones ].

===========
Make nautilus link to libsetrans.

Then on startup, nautilus calls both of those functions exactly once.
Then it has an enumeration to work with in set interfaces - have a 
drop-down box for the type, and drop-down box for the mls range.
To label a file to a non-customizable context, add a "Restore Context" 
button, which runs restorecon.




--
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:[~2006-02-28 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 21:01 Ivan Gyurdiev [this message]
2006-03-08 19:20 ` Desktop Integration Take 2 Ivan Gyurdiev
2006-03-08 19:59   ` Joe Nall
2006-03-08 21:52     ` Ivan Gyurdiev
2006-03-08 22:50       ` Joe Nall

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=4404BA44.8000503@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.