From: Daniel J Walsh <dwalsh@redhat.com>
To: Martin Orr <martin@martinorr.name>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Customizable types
Date: Mon, 19 Jan 2009 09:37:53 -0500 [thread overview]
Message-ID: <49749041.70400@redhat.com> (raw)
In-Reply-To: <4971140D.9090400@martinorr.name>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Orr wrote:
> What is the purpose of customizable types? In particular, it is not clear
> to me why the semantics are "don't relabel from a customizable type" rather
> than "don't relabel to a customizable type".
>
> Secondly, so far as I can see types are only marked as customizable when
> built into the base module. Is this intentional?
>
> Best wishes,
>
customizable_types was an old concept that we do not even implement in
Fedora any longer. The customizable_types file is empty. The idea was
that users would choose a directory to share files via http and they
would label it httpd_sys_content_t, later a autorelabel would be
triggered and the files would get relabeled. constomizable_types
entries would not get relabelled. The problem with this is that it did
not scale and mislabeled files would never get fixed if they were
customizable_types. With the introduction of semanage fcontext it
became fairly easy for the administrator to customize the labeling of
the file system and eliminated the need for customizable types.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkl0kEEACgkQrlYvE4MpobOdbQCdF8upX4NiBR+6OHMkSH7D9k9T
7i4AoNmrNgVco6zB3InlU/HNuQsGPsHw
=RhCh
-----END PGP SIGNATURE-----
--
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.
prev parent reply other threads:[~2009-01-19 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 23:11 Customizable types Martin Orr
2009-01-19 14:37 ` Daniel J Walsh [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=49749041.70400@redhat.com \
--to=dwalsh@redhat.com \
--cc=martin@martinorr.name \
--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.