ther you actually care that people know
your system uptime.
--
Stephen White \OU Compsoc System Administration Team
PGP Key ID: 0xC79E5B6A \ System Administration Co-ordinator
<[EMAIL PROTECTED]> \ http://ox.compsoc.net/~swhite/
ing a kernel recompile or upgrade. I
assume the vulnerability can't be exploited via the /proc sysctl
interface.
Unfortunately the module does nothing for the ptrace race condition,
though a module to disable ptrace would be trivial it would disable
strace and some features of gdb and so o
shared with the standard SMB File &
Printer Sharing (even read only shares) it can also be hit:
[stephen@eddie stephen]$ smbclient //eddie95/TEST -I 172.16.61.2
Added interface ip=172.16.61.1 bcast=172.16.61.255 nmask=255.255.255.0
Password:
smb: \> ls con\con
Sure enough Eddie95 BSODs. It is running Windows 95 OSR 2.
--
Stephen White <[EMAIL PROTECTED]>
it should be a fairly simple modification.
Neither of these address the real problem in the kernel, but they do
mean that sysadmins can go on allowing users to run ping without the
worry of quite such a trivial DoS.
The same problem does not appear to occur in Linux 2.2, Windows 95 or
Solaris
. It's a standard case of if you don't fully
understand the security implictations don't change the configuration.
BTW, I have lots of .shtml of the form and I certainly expect apache to run it.
This is the correct behaviour.
--
Stephen White <[EMAIL PROTECTED]>
