Difference between revisions of "Grsecurity"
| Line 15: | Line 15: | ||
* /proc/sys/kernel/grsecurity/tpe_gid | * /proc/sys/kernel/grsecurity/tpe_gid | ||
* /proc/sys/kernel/grsecurity/tpe_restrict_all | * /proc/sys/kernel/grsecurity/tpe_restrict_all | ||
| + | *[http://www.superiorpapers.com/reasons.php buy term papers] | ||
To enable TPE feature in a standard way just type: | To enable TPE feature in a standard way just type: | ||
Revision as of 11:25, 22 August 2010
There is a huge demand from people for support of grsecurity on OpenVZ. However, unfortunately, grsecurity patch doesn't work as is (nor even applies) with OpenVZ kernel. There were some efforts of supporting grsec in bug #607, but failed and the grsecurity patch was never stable with OpenVZ.
So instead OpenVZ team selected another approach. We port the features of grsecurity most requested by users and add them, maintain, document and support.
TPE (Trusted Path Execution)
Starting from 2.6.18-028stab047.1 stable kernels OpenVZ kernels support TPE grsecurity feature out of the box. Which means root user can configure TPE inside VE as usual, i.e. via the following /proc files:
- /proc/sys/kernel/grsecurity/grsec_lock
- /proc/sys/kernel/grsecurity/tpe
- /proc/sys/kernel/grsecurity/tpe_gid
- /proc/sys/kernel/grsecurity/tpe_restrict_all
- buy term papers
To enable TPE feature in a standard way just type:
# echo <GID> > /proc/sys/kernel/grsecurity/tpe_gid # echo 1 > /proc/sys/kernel/grsecurity/tpe ' lock grsecurity settings # echo 1 > /proc/sys/kernel/grsecurity/grsec_lock
