All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2 3/5] Adding dracut policy
Date: Mon, 25 Jun 2012 11:29:27 -0400	[thread overview]
Message-ID: <4FE883D7.9060808@redhat.com> (raw)
In-Reply-To: <1340636009.2003.5.camel@x220.mydomain.internal>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/25/2012 10:53 AM, Dominick Grift wrote:
> On Mon, 2012-06-25 at 16:49 +0200, Dominick Grift wrote:
>>>>> +seutil_exec_setfiles(dracut_t)
>>>> So you allow it to run setfiles in the dracut domain, but you dont
>>>> allow the dracut domain to relabelfrom and -to anything?
>>> 
>>> It's not about executing; dracut uses "ldd" to scan for libraries it
>>> needs in the initramfs. But using "ldd" means that ldd (underlyingly)
>>> executes the files. Hence, the need for _exec (but not for _domtrans or
>>> functionality).
>>> 
>> 
>> I think you want mmap ( create a seutil_check_exec_setfiles() or 
>> something)
>> 
>> mmap provides only execute exec provides execute as well as
>> execute_no_trans
>> 
>> i think that , if i understand you correctly, it doesnt need the 
>> execute_no_trans
>> 
> 
> but nevertheless, push comes to shove, dracut should probably optionally be
> allowed to (really) execute setfiles and be allowed to 
> dev_relabel_all_devices
> 
> In at least old fedora it mounts /sysroot/dev, restores context of /dev and
> then loads policy (if i am not mistaken)
> 
>> 
> 
> 
> _______________________________________________ refpolicy mailing list 
> refpolicy at oss.tresys.com http://oss.tresys.com/mailman/listinfo/refpolicy
> 

Yes although I think that is being done by systemd or systemd-udev now.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/og9cACgkQrlYvE4MpobOgFQCfc/1HkxLjTKynRsy9qtG8LaN+
ZRwAnA6TgB/A1Z3Mv6m7Gv5yJZXwql12
=J4oz
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-06-25 15:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-24 18:03 [refpolicy] [PATCH v2 0/5] Support dracut domain Sven Vermeulen
2012-06-24 18:03 ` [refpolicy] [PATCH v2 1/5] Add read interface for udev rules Sven Vermeulen
2012-06-24 19:28   ` Dominick Grift
2012-06-24 18:04 ` [refpolicy] [PATCH v2 2/5] Support listing module configuration files Sven Vermeulen
2012-06-24 19:32   ` Dominick Grift
2012-06-24 18:04 ` [refpolicy] [PATCH v2 3/5] Adding dracut policy Sven Vermeulen
2012-06-24 19:42   ` Dominick Grift
2012-06-25  8:24     ` Miroslav Grepl
2012-06-25  8:36       ` Dominick Grift
2012-06-25 13:42         ` Daniel J Walsh
2012-06-25 14:35       ` Sven Vermeulen
2012-06-25 14:31     ` Sven Vermeulen
2012-06-25 14:49       ` Dominick Grift
2012-06-25 14:53         ` Dominick Grift
2012-06-25 15:29           ` Daniel J Walsh [this message]
2012-06-25 16:29           ` Sven Vermeulen
2012-06-25 16:36             ` Dominick Grift
2012-06-25 20:38     ` Sven Vermeulen
2012-06-24 18:05 ` [refpolicy] [PATCH v2 4/5] Grant dracut_manage_tmp_files to domains called by dracut Sven Vermeulen
2012-06-25 13:44   ` Daniel J Walsh
2012-06-24 18:05 ` [refpolicy] [PATCH v2 5/5] Allow sysadm_t to call dracut and transition to dracut_t Sven Vermeulen

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=4FE883D7.9060808@redhat.com \
    --to=dwalsh@redhat.com \
    --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.