Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Olaf Kirch (okir_at_suse.de)
Date: Wed Nov 13 2002 - 09:31:03 CST
There seem to be two problems here.
> Now the umask seems to be 033 (unless I define a different value in the
> file /etc/fstab). Unfortunately this umask is applied to directories,
> too. So unprivileged users are unable to read any file on the mounted
I think it's a good idea to set a umask option in fstab anyway, but
I agree that the documented default behavior should have been
> Setting the umask to 023 I can enable some users to read these files;
> but now all files get the x-bit as well, a thing I'd like to avoid.
Now that's a different issue, most likely has nothing to do with
the update. If it sets the x bit on regular files now, then it probably
did so before the update, too.
-- Olaf Kirch | Anyone who has had to work with X.509 has probably okirsuse.de | experienced what can best be described as ---------------+ ISO water torture. -- Peter Gutmann
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-helpsuse.com Security-related bug reports go to securitysuse.de, not here