Buchan Milne wrote:
> 
> Or maybe /usr/bin is not in your tcsh path? It should be able to call
> then explicitly.

Yes, calling the command explicitly (EX: /usr/bin/test) made it run,
because /usr/bin/test has permissions 755).

/usr/bin was also in the path, but, As I explained previously, it was
unreachable because of the directory permissions in msec level 4(744)

> Bash should not be suid, which would be a very big risk

Precisely my point. Is there any other explanation for bash being able
to
execute (= look into) a 744 directory owned by root?

> !! Have you checked the permissions on bash??

Now that I have switched to msec level 3 both tcsh and bash executables
look fine (rwxr-xr-x). Unfortunately, I did not  test it when in msec 4.

Is anybody on the list using msec level 4?

        Ciao,

                Marco Fioretti

Keep in touch with http://mandrakeforum.com: 
Subscribe the "[EMAIL PROTECTED]" mailing list.

Reply via email to