Re: klog under linux 2.6.0-test11
George Georgalis <[email protected]>
| Newsgroups | gmane.comp.misc.pape.general |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Dec 08, 2003 at 01:17:52PM +0100, Gerrit Pape wrote: >On Mon, Dec 08, 2003 at 11:05:26AM +0100, Lukas Beeler wrote: >> This also happens for me. Iam using 2.6.0-test[8-11], without >> further patches. No obscure security patches whatsoever applied. >> I ``fixed'' the problem by running socklog-klog as root. Didn't >> investigate it further, because i lacked time to do so. > >Indeed. I found a machine running linux 2.6.0-test8: > # uname -r > 2.6.0-test8 > # ls -l /tmp/testfile > -r-------- 1 root root 49 Dec 8 11:48 /tmp/testfile > # (su -c cat nobody) </tmp/testfile > foo bar > # > >fine, but: > # ls -l /proc/kmsg > -r-------- 1 root root 0 Nov 24 10:00 /proc/kmsg > # (su -c cat nobody) </proc/kmsg > cat: -: Operation not permitted > # > >with kernel 2.4: > # uname -r > 2.4.22 > # (su -c cat nobody) </proc/kmsg > >it works fine. > >I'm curious if this change to the proc file-system is intended. I've not patched 2.6.0-test11, and tried many variations of the config (including no security features) The other odd thing is the permissions don't seem to matter.... -r-------- 1 root root 0 Dec 6 17:52 /proc/kmsg I tried changing the ownership: -r-------- 1 log root 0 Dec 6 17:53 /proc/kmsg Even opening it up completely: -r--r--r-- 1 log root 0 Dec 6 17:57 /proc/kmsg same problem. // George -- GEORGE GEORGALIS, System Admin/Architect cell: 646-331-2027 <IXOYE>< Security Services, Web, Mail, mailto:[email protected] Multimedia, DB, DNS and Metrics. http://www.galis.org/george