Re: [Noffle-devel] Big Problems with noffle 1

[Mirko L. <mir...@we...>]

Jim Hague wrote:
> The thing is, I don't see how the umask (well, any sane one) could matter.
> After all, noffle should be suid news by that stage and creating directories
> owned by news.

Well, maybe I'm wrong blaming the umask for Thorsten's problems.

> One thing does occur to me, though, looking at the leafnode and the noffle
> problems. Could something have been through and reset the suid bit on the
> executable? Some sort of security checking process?

Suse 7.0 (the version I use) uses the sh-script /sbin/SuSEconfig.
It fixes ownership and permissions of the files listed in
/etc/permissions.* and /etc/permissions.d/* . An example:

$ cat /etc/permissions.d/tetex 
/var/lib/texmf/                 root.root               1755
/var/lib/texmf/ls-R             root.root               0666
[.. and so on ..]

Since Jim's noffle.rpm for Redhat 7.2 doesn't contain such a list, it's
files won't be checked. There is no default permission or ownership for
unknown files. I hope this hasn't been changed in Thorsten's Suse 8.0.


friendly regards,

Mirko