no, there should be no danger to give rx permissions on directories under
/usr/src and r permission on files there too.
any user should be able to compile a program if he needs to.
But if for security reasons you don't want people compiling things on
your machine then you should not install ANY development tool (and
therefore compile your kernels on another computer). Many hacks (stack
overflow) imply compiling programs and if this is not possible on the
attacked system, the hacker has to compile on another system and
transfert the binary wich may be a potential problem for him.
-----Message d'origine-----
De: James Clifford [SMTP:[EMAIL PROTECTED]]
Date: mercredi 12 ao�t 1998 13:39
�: [EMAIL PROTECTED]
Objet: /usr/src permissions
Is there any reason why /usr/src wouldn't have the executable permission
set for other users? Trying to compile a program as with my personal
account failed when I included stdlib.h because I didn't have permission
to access some other header files that were buried in /usr/src. Root had
no problems, so I compiled the program with root then changed permissions
on /usr/src so that I could compile with my personal account. Is this a
bad thing to do?
-------------------------------------------------------------------------
James Clifford | http://www.tripod.com/~MrBobo
[EMAIL PROTECTED] | The best way to make your dreams come true is
[EMAIL PROTECTED] | to wake up. - Paul Valery
