* refpolicy flask generator script
@ 2017-04-11 14:47 Christian Göttsche
2017-04-11 15:05 ` Stephen Smalley
0 siblings, 1 reply; 2+ messages in thread
From: Christian Göttsche @ 2017-04-11 14:47 UTC (permalink / raw)
To: selinux
Is the flask generator script[1] still needed;
or can it be removed or moved into the kernel repo?
related: https://github.com/TresysTechnology/refpolicy/issues/49
[1] https://github.com/TresysTechnology/refpolicy/blob/master/policy/flask/flask.py
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: refpolicy flask generator script
2017-04-11 14:47 refpolicy flask generator script Christian Göttsche
@ 2017-04-11 15:05 ` Stephen Smalley
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Smalley @ 2017-04-11 15:05 UTC (permalink / raw)
To: Christian Göttsche, selinux
On Tue, 2017-04-11 at 16:47 +0200, Christian Göttsche wrote:
> Is the flask generator script[1] still needed;
> or can it be removed or moved into the kernel repo?
>
> related: https://github.com/TresysTechnology/refpolicy/issues/49
>
> [1] https://github.com/TresysTechnology/refpolicy/blob/master/policy/
> flask/flask.py
It should be obsoleted by the dynamic class/perm mapping support (both
kernel and userspace). The libselinux headers have been shipping with
#warnings for a while now, and the kernel ones are automatically
generated at build time via the genheaders tool in the kernel tree from
the classmap.h definitions instead.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-04-11 15:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-11 14:47 refpolicy flask generator script Christian Göttsche
2017-04-11 15:05 ` Stephen Smalley
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.