From: aranea@aixah.de (Luis Ressel)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Updated loopback mount patches
Date: Sat, 1 Feb 2014 15:32:37 +0100 [thread overview]
Message-ID: <20140201153237.498eb66a@gentp.lnet> (raw)
In-Reply-To: <1391262624-4486-1-git-send-email-aranea@aixah.de>
For mounting my squashfs images (which don't contain xattrs, even
though squashfs has support for those), I currently also need
"allow mount_t unlabeled_t:filesystem relabelfrom;".
kernel/filesystem.te mentions a filesystem "squash", dating back to
2007. Since then, the name seems to have changed to "squashfs".
Most likely "sed -i s/squash/squashfs/g kernel/filesystem.te" will do.
I haven't tested it, though (as I haven't managed yet to compile the
whole policy manually).
--
Luis Ressel <aranea@aixah.de>
GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5 7F90 3029 B5BD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20140201/d30ddd28/attachment.bin
prev parent reply other threads:[~2014-02-01 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 13:50 [refpolicy] Updated loopback mount patches Luis Ressel
2014-02-01 13:50 ` [refpolicy] [PATCH 1/4] kernel/devices.if: Add dev_rw_loop_control interface Luis Ressel
2014-02-08 15:51 ` Christopher J. PeBenito
2014-02-01 13:50 ` [refpolicy] [PATCH 2/4] system/mount.if: Add mount_read_mount_loopback interface Luis Ressel
2014-02-08 15:51 ` Christopher J. PeBenito
2014-02-01 13:50 ` [refpolicy] [PATCH 3/4] Allow mount_t usage of /dev/loop-control Luis Ressel
2014-02-08 15:51 ` Christopher J. PeBenito
2014-02-01 13:50 ` [refpolicy] [PATCH 4/4] Grant kernel_t necessary permissions for loopback mounts Luis Ressel
2014-02-08 15:51 ` Christopher J. PeBenito
2014-02-01 14:32 ` Luis Ressel [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=20140201153237.498eb66a@gentp.lnet \
--to=aranea@aixah.de \
--cc=refpolicy@oss.tresys.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.