[refpolicy] Generation of FLASK entries

[Martin Christian]

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

Hi,

I'm trying to understand the process how the ref policy is built.
However, I'm wondering how you keep the flask entries up-to-date with
the kernel? To me it seems like you always use the fixed access vector
definitions from policy/flask, isn't it? This might cause the policy
being out of sync with the kernel, e. g.: Kernel 2.6.37 introduced the
permission syslog for class capabiliy2.

Regards,

Martin.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOA2SiAAoJEGpTkDITRjmooFQIAMIlHA60M0fb8uZNJwbrQJmu
fU/JSsKM1gv7Hx1Hd4bcz48yY/9WT5Pop4v2T1K812sYcfwqR/nwAy9PsOQy2p34
QCUgN0EzbhV6rjcXb5mCeQuOW1wfTeXyTrMqhIiaenh+ePEZdvA6hPE6SnepjiMw
fVl9gyIMw0pCviX0abflJg0l+lJh86XVeLOikp9X6QG2mCUV0dgursXKe/yeiC9O
Vpm/DEL/B3qvAU9RE0EFsnHKNAg+BMfSaedlZm4igNmVo3KxjFYjDjDa1xhX6P7Y
oGNFkbJ+rhhAkzuDR96Sqvr/naLPyvdZfTA3b7X/AfdL8cAbMFb/bIywe6S6RjY=
=xZUX
-----END PGP SIGNATURE-----