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: Wed, 13 Apr 2016 19:10:11 +0200 [thread overview]
Message-ID: <570E7D73.5060302@gmail.com> (raw)
In-Reply-To: <570E7B15.6090906@tycho.nsa.gov>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 04/13/2016 07:00 PM, Stephen Smalley wrote:
> On 04/13/2016 12:34 PM, Dominick Grift wrote:
>> On 04/12/2016 04:35 PM, Christopher J. PeBenito wrote:
>>
>>> Right, the script that refpolicy has is only used on
>>> monolithic builds.
>>
>>
>> As I recall, last time i tried it, it was not working on a
>> redhat-based system. Probably bit-rot has set in. There is also
>> some hard-coding going on in there i believe.
>>
>> Someone with c-skills should rewrite it in c, make it truly
>> portable. That way it can be used with both monolithic as well as
>> modular policy (i don't mean binary-based module policy here but
>> text-based module policy that otherwise does not require the
>> presence of semodule)
>
> Even CIL-based modules are installed via semodule and managed via
> libsemanage, and libsemanage already contains a C implementation
> of genhomedircon.
>
>
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
.
- --
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
iQGcBAEBCAAGBQJXDn1vAAoJECV0jlU3+UdpkP4MAIhmW/ghl9/pVBVSX+56lZEB
ns9znLpwUSv50kcYDh9e8lfWrIOlJGgXD86D2pnCU2AjJbxvBWaEQpPw0Z0c+Vmy
M8NvBTqm763mTZ2ANgGFjWpE0cAOAFIHBmfNhacl6fyUwVLfxZA/locUh9SJIsqd
AhSx+lt9t2uMxB7W2PoCf6Bwpz+fQDbnD+3vaU5ZIcu/sNYGYd4Pmf4jYl38QR1P
vxCIrj4OTJrT7w0A0/J98d7jBnLsvvb63Jjm+5HP3PP5mHn0DGu6/qEBKJcuYWPP
tyRIVzlvreRrrVoF6u9BtgDD7+/1XXco20yoQanXCr2fhox5OkW8/TerK9KEcbwE
a4MZyDPlTrpthprznvSSaCo5uK6xCoaIBR9GjBlU3L/CUzI6ZioEoVwX9wxMpskA
TGtYRJyCVlrxYCy7ec/qEBY3vTg61DsTwq2fL84F+11NoJofIBuY2AwqQ5WpJmwN
WRtkEVQWqtxE1cybXhiQX0UIlBt3uqcHO6+Xr5TYSQ==
=u/g3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-04-13 17:10 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 [this message]
2016-04-13 17:18 ` Dominick Grift
2016-04-13 18:25 ` Dominick Grift
2016-04-17 10:12 ` Dominick Grift
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=570E7D73.5060302@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.