> Most of my web content is owned and +rwx by me, not the web server. But
> most of the content is o+rx so they can be served up. Works, but I'm not
> sure if it's the most secure approach.
just a little thing, but unless these are actually apps that can be (and
that you want to be) executed by the server, there is no need to make them
'x'. if you are the only person working on these files, then something
like '644' (-rw-r--r--) should be fine.
you can fix this in one fell swope with something like 'find . -type f
-exec chmod 664 {} \;' for the files and 'find . -type d -exec chmod 775
{} \;' for the directories.
if you are using bash then you might be able to get away with something
like 'chmod 644 $(find . -type f)' and 'chmod 755 $(find . -type d)' but
i find the find command to be more reliable.
> _______________________________________________________________
> Thank goodness my government knows what's good for me.
> for a moment I was worried I was going to have to think for myself!
heh.
cheers,
sach
--
"...rights are won, not granted, and power will seek any opportunity to reduce them."
- Noam Chomsky
_______________________________________________
Bits mailing list
[EMAIL PROTECTED]
http://www.sugoi.org/mailman/listinfo/bits
