Dominic Coulombe wrote:
The C program is a good idea but :
1) remove the gcc and other build tools after the development !
2) you will still need Tripwire to be sure nobody replaces your binary...
or use a RR dasd.
The SETUID bit is a good idea if you are sure that the binary is not
modified by a malicious user.
Prsumably such an individual would need to be root and hence not need
the SETUID bit.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
