From: martin.christian@secunet.com (Martin Christian)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Generation of FLASK entries
Date: Thu, 23 Jun 2011 18:07:06 +0200 [thread overview]
Message-ID: <4E0364AA.8080207@secunet.com> (raw)
-----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-----
next reply other threads:[~2011-06-23 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 16:07 Martin Christian [this message]
2011-06-24 13:13 ` [refpolicy] Generation of FLASK entries Christopher J. PeBenito
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=4E0364AA.8080207@secunet.com \
--to=martin.christian@secunet.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.