aboutsummaryrefslogtreecommitdiffstats
path: root/rules
diff options
context:
space:
mode:
authorAndre Przywara <andre.przywara@amd.com>2009-04-24 00:29:53 +0200
committerKay Sievers <kay.sievers@vrfy.org>2009-04-24 00:29:53 +0200
commit57ec3a57f1caa0e325e5ac8a7f54761148b36b1b (patch)
tree677f78e845c54c451ad3a1c6c1a17675b6465f9b /rules
parent19d7e87cc0ef364fb13a18411cb165b2427b3529 (diff)
downloadudev-57ec3a57f1caa0e325e5ac8a7f54761148b36b1b.tar.gz
rules: create /dev/cpu/<n>/cpuid world readable
I don't see any security implications, to be actually useful, /dev/cpu/<n>/cpuid should be world readable. The cpuid instruction can be called from userspace anyway, so there is nothing to hide. The device does not support any write operation, so 0444 should suffice. Signed-off-by: Andre Przywara <andre.przywara@amd.com>
Diffstat (limited to 'rules')
-rw-r--r--rules/rules.d/50-udev-default.rules2
1 files changed, 1 insertions, 1 deletions
diff --git a/rules/rules.d/50-udev-default.rules b/rules/rules.d/50-udev-default.rules
index abc5113c..6bf45cce 100644
--- a/rules/rules.d/50-udev-default.rules
+++ b/rules/rules.d/50-udev-default.rules
@@ -94,7 +94,7 @@ SUBSYSTEM=="aoe", KERNEL=="err", MODE="0440"
KERNEL=="tun", NAME="net/%k", MODE="0666"
# CPU
-KERNEL=="cpu[0-9]*", NAME="cpu/%n/cpuid"
+KERNEL=="cpu[0-9]*", NAME="cpu/%n/cpuid", MODE="0444"
KERNEL=="msr[0-9]*", NAME="cpu/%n/msr"
KERNEL=="microcode", NAME="cpu/microcode", MODE="0600"