Your message dated Mon, 28 May 2007 18:45:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Why is kern.log o-r ?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: sysklogd
Version: 1.4.1-15
Severity: minor
File: /etc/cron.daily/sysklogd
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kernel log messages can be read by anyone on the system with the aid of,
e.g., dmesg. Why is kern.log o-r?
- -- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (130, 'unstable'), (120, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-bohr
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages sysklogd depends on:
ii klogd [linux-kernel-log-dae 1.4.1-15 Kernel Logging Daemon
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBnfOb+z+IwlXqWf4RAidaAJ4pVl30JEQ+jGbKmG7TB4i0TCHABACfXoF0
Q50UvNnnUbl3M3Ym8hnvMas=
=X70G
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Anthony DeRobertis wrote:
> Kernel log messages can be read by anyone on the system with the aid of,
> e.g., dmesg. Why is kern.log o-r?
Because no special exception is implemented for kernel logs and other
log files are not world readable. Also, only the last 8k of kernel
logs are publically readable through dmesg.
Regards,
Joey
--
It's practically impossible to look at a penguin and feel angry.
Please always Cc to me when replying to me on the lists.
--- End Message ---
