---
May 15th, 2013, 17:50
سلام
شرکت BetterLinuxTM (http://www.betterlinux.com/) امروز برای من ایمیلی رو با عنوان CentOS kernel security exploit ارسال کرده که بنده عین ایمیل رو براتون نقل قول میکنم .
Dear BetterLinux Beta Customer,
A vulnerability has been discovered in stock CentOS and RHEL 2.6.32.X kernels (and consequently in the BetterLinux kernel) that requires an immediate security response. While we wait for upstream vendors to address the issue, please use this temporary work-around to secure your systems:
Using the
sysctlutility, alter the the
perf_event_paranoidvariable. In part, this variable determines whether you:
Disallow cpu events for unprivileged users
Disallow kernel profiling for unprivileged users
Choose option 2, which essentially makes the
perfsystem usable only by root:
sysctl kernel.perf_event_paranoid=2
Unfortunately, this variable resets upon reboot. Here are three responses to that inconvenience:
Manually change the variable after every boot
Add the
sysctlinstruction into a system RC script, OR
Simply add the instruction into
/etc/sysctl.conf.
Redhat is now testing a fix, and CentOS will not be far behind. We apologize for any inconvenience.
The BetterLinux Team
شرکت BetterLinuxTM (http://www.betterlinux.com/) امروز برای من ایمیلی رو با عنوان CentOS kernel security exploit ارسال کرده که بنده عین ایمیل رو براتون نقل قول میکنم .
Dear BetterLinux Beta Customer,
A vulnerability has been discovered in stock CentOS and RHEL 2.6.32.X kernels (and consequently in the BetterLinux kernel) that requires an immediate security response. While we wait for upstream vendors to address the issue, please use this temporary work-around to secure your systems:
Using the
sysctlutility, alter the the
perf_event_paranoidvariable. In part, this variable determines whether you:
Disallow cpu events for unprivileged users
Disallow kernel profiling for unprivileged users
Choose option 2, which essentially makes the
perfsystem usable only by root:
sysctl kernel.perf_event_paranoid=2
Unfortunately, this variable resets upon reboot. Here are three responses to that inconvenience:
Manually change the variable after every boot
Add the
sysctlinstruction into a system RC script, OR
Simply add the instruction into
/etc/sysctl.conf.
Redhat is now testing a fix, and CentOS will not be far behind. We apologize for any inconvenience.
The BetterLinux Team