From: Paul Moore <paul.moore@hp.com>
To: James Antill <jantill@redhat.com>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: Tar storage of SELinux context, translated or not
Date: Wed, 10 Jan 2007 12:33:40 -0500 [thread overview]
Message-ID: <200701101233.40143.paul.moore@hp.com> (raw)
In-Reply-To: <1168448023.13080.33.camel@code.and.org>
On Wednesday, January 10 2007 11:53 am, James Antill wrote:
> As some of you know, I have done patches to make GNUtar able to
> save/restore ACLs, SELinux context and generic user xattrs. I've
> recently had to fixup the ACL support for compatibility with star etc.,
> and for a couple of reasons that got me thinking about the SELinux
> support as well.
>
> I had originally decided that the SELinux security context should be
> stored in translated form, Ie. getfilecon => tar => setfilecon, my
> thinking was that if you want to store something over a long period this
> is the better format ... but as I think more about it now I'm not 100%
> convinced (for instance, AIUI ipsec etc. uses raw format to distribute
> context between machines).
> With the current changes, this is a great time to change it (but I
> really, really, don't want to have an option either way) ... if we want
> to. So should I change it to non-translated?
Regardless of what the tar command does, you could always have the tarfile
format allow either (store both the context string as well as a flag
indicating if the context was translated). This way if things change down
the road all the existing tar files are still valid.
--
paul moore
linux security @ hp
--
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:[~2007-01-10 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 16:53 Tar storage of SELinux context, translated or not James Antill
2007-01-10 17:33 ` Paul Moore [this message]
2007-01-10 17:43 ` Stephen Smalley
2007-01-10 17:56 ` Casey Schaufler
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=200701101233.40143.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=jantill@redhat.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.