Reasons for CHMODING
CHMODing files can be done for a variety of reasons. You can CHMOD files to
do things such as: mark them executable, give them write permission,
restrict access to them, and a variety of other reasons. It is important to
note that chmoding is nearly impossible to avoid. If you are trying to run a
certain cgi script it could require execute permissions on the script
itself, write permissions on a directory, and read on an informational page.
Your cgi scripts should contain the proper documentation to inform you of
the proper CHMOD's.
List of CHMOD's and what they mean.
chmod 777 filename The file is available for Read, Write, and Execute for
the owner, group, and world.
chmod 755 filename The file is available for Read, Write, and Execute for
the owner; and Read and Execute only for the group and world.
chmod 644 filename The file is available for Read and Write for the owner,
and Read only for the group and world.
chmod 666 filename The file is available for Read and Write for the owner,
group, and world. I wonder if the 666 number is just a coincidence. Anybody
can create havoc with your files with this wide-open permission mask.
