From: Dominick Grift <dac.override@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Subject: Re: genhomedircon USERID and USERNAME patches
Date: Sun, 17 Apr 2016 12:12:43 +0200 [thread overview]
Message-ID: <5713619B.3090604@gmail.com> (raw)
In-Reply-To: <570E8F36.3060609@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 04/13/2016 08:25 PM, Dominick Grift wrote:
> On 04/13/2016 07:18 PM, Dominick Grift wrote:
>
>>> Let me correct that:
>
>>> "Even CIL-based modules can be installed via semodule and
>>> managed via libsemanage, and libsemanage already contains a C
>>> implementation of genhomedircon."
>
>
>>> that is not my point though. My point is: since we need a
>>> working genhomedircon for monolithic policy, we might cease
>>> the opportunity to also support text-based module policy which
>>> can be installed via semodule and managed via libsemanage, but
>>> does not strictly require that .
>
>
>> Make that "seize" instead (i think)
>
>
> I just realized that i do not have to bring CIL into the equation
> here. We can keep it nice, simple and to the point. Refpolicy
> genhomedircon needs to be updated (and needs just a general review
> to make it work again on modern distributions) as well to make this
> new functionality also work with monolithic policy.
>
> Also since were on the discussion of genhomedircon, I might be
> wrong here, but I believe genhomedircon cannot currently deal with
> %group entries in seusers.
>
>
I think we should also generate file context specs for user mail spool
(is currently not done AFAIK in common module policy).
But if genhomedircon would not hardcode keywords and identifiers, then
i could accept them through the command line options and map it to
some hardcoded initial identifiers where/if needed
then one could specify on the command line the keyword, and any other
identifiers. So that is a bit more flexible so that when in the future
we get other instances where we need to generate contexts for some
location we dont have to edit the script we can just pass it some
additional new options. But yes then i suppose it would need to be a
standalone script. Added value there is that we then no longer have to
maintain to genhomedircon instances, one for libsemanage and one for
monolitic policy and text-based module policy.
- --
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBCAAGBQJXE2GXAAoJECV0jlU3+UdpHjML/0WTMGgEjjkgPuLduoOTxGjA
VBiiAOSIrrwh//TxXbbVxy1G46AHAD8SxBfC8TRCnAYMP01EVHpst7lLwXP4aDvH
a0Nhv7NV3nfdKCMuYKcXmGjPvkMD2u5v2JOpQjAM4s1AHxCm5irKq7rHZLeWfuVO
Ry4s0tQNRme8niHcr7I9jk50+ijxrUyKgh2CZQw0dmJ80nGCDXrbmGRYQYVY6Aw7
yNGhu7eoMbXd9yN5k9UAtT+kvLuD9gxahfokKECNqqLwWzf7ttP5idkDS8GQLYVM
OfogT6TKeQznqnU5y3ojTEVHy+2tjwjntVX4OSeBVietWH1Sulrv0SX0YhqjiYbQ
NE4GZi67JvExGXbGKSitMg6kSmivguUVIb7DAVviLW5FrHPWGZMybRFf/LtyZ3Ay
+GCgIFpeMn0933B4T6O6fZozcqpD66aFF9DWNvtQ2p9hIWzFNdxGwgg0B1gJJ0CO
eVReqMaR+15C1xiAoZz/C6Pa0r+qzTM8+0GorwEQ5A==
=ggrX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-04-17 10:12 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 9:36 genhomedircon uid template Jason Zaman
2016-02-01 19:30 ` Stephen Smalley
2016-02-02 6:26 ` Jason Zaman
2016-02-02 13:57 ` Christopher J. PeBenito
2016-02-02 15:03 ` Stephen Smalley
2016-02-02 20:39 ` Nicolas Iooss
2016-04-08 16:05 ` genhomedircon USERID and USERNAME patches Jason Zaman
2016-04-08 16:05 ` [PATCH 1/7] genhomedircon: factor out common replacement code Jason Zaman
2016-04-08 16:05 ` [PATCH 2/7] genhomedircon: move fallback user to genhomedircon_user_entry_t Jason Zaman
2016-04-08 16:05 ` [PATCH 3/7] genhomedircon: rename FALLBACK #defines consistent with struct Jason Zaman
2016-04-08 16:05 ` [PATCH 4/7] genhomedircon: make all write context funcs take user_entry struct Jason Zaman
2016-04-08 16:05 ` [PATCH 5/7] genhomedircon: Add uid and gid to struct user_entry Jason Zaman
2016-04-08 16:05 ` [PATCH 6/7] genhomedircon: make USERID, USERNAME context lists Jason Zaman
2016-04-08 16:05 ` [PATCH 7/7] genhomedircon: write contexts for username and userid Jason Zaman
2016-04-11 21:44 ` genhomedircon USERID and USERNAME patches Nicolas Iooss
2016-04-12 7:56 ` Dominick Grift
2016-04-12 11:51 ` Jason Zaman
2016-04-12 12:57 ` Stephen Smalley
2016-04-12 14:35 ` Christopher J. PeBenito
2016-04-13 16:34 ` Dominick Grift
2016-04-13 17:00 ` Stephen Smalley
2016-04-13 17:10 ` Dominick Grift
2016-04-13 17:18 ` Dominick Grift
2016-04-13 18:25 ` Dominick Grift
2016-04-17 10:12 ` Dominick Grift [this message]
2016-04-17 12:03 ` Dominick Grift
2016-04-17 19:19 ` Dominick Grift
2016-04-18 6:23 ` Dominick Grift
2016-04-23 6:04 ` genhomedircon USERID and USERNAME patches v2 Jason Zaman
2016-04-23 6:04 ` [PATCH v2 1/8] genhomedircon: factor out common replacement code Jason Zaman
2016-04-23 6:04 ` [PATCH v2 2/8] genhomedircon: move fallback user to genhomedircon_user_entry_t Jason Zaman
2016-04-29 16:54 ` Stephen Smalley
2016-04-29 19:23 ` Jason Zaman
2016-04-29 20:29 ` Stephen Smalley
2016-04-23 6:04 ` [PATCH v2 3/8] genhomedircon: rename FALLBACK #defines consistent with struct Jason Zaman
2016-04-23 6:04 ` [PATCH v2 4/8] genhomedircon: make all write context funcs take user_entry struct Jason Zaman
2016-04-23 6:04 ` [PATCH v2 5/8] genhomedircon: Add uid and gid to struct user_entry Jason Zaman
2016-04-27 17:04 ` Stephen Smalley
2016-04-28 17:53 ` Jason Zaman
2016-04-28 18:13 ` Stephen Smalley
2016-04-29 12:01 ` Jason Zaman
2016-04-23 6:04 ` [PATCH v2 6/8] genhomedircon: make USERID, USERNAME context lists Jason Zaman
2016-04-23 6:04 ` [PATCH v2 7/8] genhomedircon: write contexts for username and userid Jason Zaman
2016-04-23 6:04 ` [PATCH v2 8/8] genhomedircon: fix FALLBACK_NAME regex Jason Zaman
2016-04-26 22:03 ` genhomedircon USERID and USERNAME patches v2 Nicolas Iooss
2016-04-29 12:04 ` [PATCH v3 5/8] genhomedircon: Add uid and gid to struct user_entry Jason Zaman
2016-04-29 20:28 ` Stephen Smalley
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=5713619B.3090604@gmail.com \
--to=dac.override@gmail.com \
--cc=sds@tycho.nsa.gov \
--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.