BUG kernel 2.4.3-2.4.6!! - Fw: Re: umask for init

[Nick Name <nick.name@inwind.it>]

Leggete se avete un kernel 2.4.3-2.4.6! Il bug é gravuccio :))) Le prime
tre righe (quelle quotate) sono le più importanti, il resto sono i miei
più o meno utili sproloqui su check e soluzione. debian-security per
riferimenti

Ciao!

Vincenzo

---

Date: Tue, 24 Jul 2001 02:24:41 +0200
From: Nick Name <nick.name@inwind.it>
To: Debian security <debian-security@lists.debian.org>
Subject: Re: umask for init


Il giorno Mon, 23 Jul 2001 15:58:33 -0800 Ethan Benson <erbenson@alaska.net> ha scritto:

> kernels 2.4.3 - 2.4.6 set the umask to 000 so any thread/process
> created by the kernel, including init started with umask 000 and
> remained that way unless init changed it itself.
> 

Sincerely thanks. I did not know of this bug and I got a machine running 
2.4.6.

For others, here's a quick way to test if you have the bug:

In /etc/inittab:

# Action on special keypress (ALT-UpArrow).
kb::kbrequest:/usr/bin/touch /tmp/crack_this_system_with_me

then, as root obviously:

telinit q

Then press Alt+UpArrow and 

ls -la /tmp/crack_this_system_with_me

If this is rw-rw-rw well, you will agree, you have the feature
... er ... the bug! Tell me this and your ip, and do nothing else,
I'll repair your system :))))


More seriously, a quick fix could be, if you can't switch back 2.2.19 or 
go forward 2.4.7, to mv /sbin/init /sbin/good_init and put in /sbin/init 
a script like this, everything is untested of course:

#!/bin/sh
umask 022
exec /sbin/init