Ovo sam naso danas...

> Is there a way where I can give chmod 777 permission
> to all files in a given folder so I do not have to
> type chmod 777 filename for each file. I have about
> 100 plus files in a given folder that needs chmod
> 777 permission. Is there a better way? If not there
> goes my weekend.



777 is dangerous. You don't really want to do that unless you are very sure everything is secure, because 777 will give ANYONE access to those files.

But,if you want to chmod an entire directory, you cando something like:

%chmod 770 -R aDirectory/

or
%chmod 770 *

or
%man chmod

remember, man (as in manual, not male ) is your best friend.

Chris

Kid read a unix tutorial please! just type:

chmod 777 *


Using the * wildcard will... by the way, this is not the proper list to ask this kind of questions, some people may feel offended

Saludos

Claudio.

Alright, so say I tell you that to have attachments work properly, your attachment folder needs to be 777.  The first thing people ask me is...

  - Isn't this a security risk?
The short answer is: no, not really... it isn't.  Keep reading for the long answer.

  - So, what, you're saying EVERYTHING should be 777?!?
Not hardly.  Just the forum's directory, and all the files and directories inside it.  Not, of course, that you should do this - but it won't matter much if you do, so long as your server is configured reasonably correctly.

  - But... wait a minute.  The three numbers stand for "Owner," "Group," and "Everyone."  Doesn't that mean anyone can write to the files if I make it 777? (writable by all!?)
Well, technically, yes.  But, the person first has to get into your server and be able to touch the file in the first place.  They also have to have access to the directory the file is in, and the directory that file is in.  At some point, you should have a directory (probably your username) which isn't 777.

  - Isn't it safer, at least, not to use 777?  What if a hacker got in?!
If a hacker gets in and wants to cause you trouble.... there is nothing you can do.  You can have the file permissions as strict as you want, but the database will be wide open.  So, yeah... you can protect the files that don't change from being deleted, but not your posts.
Which is more important?  The files you can download again from here or the data you cannot get back?

  - Isn't it unlikely a hacker would get into my server so much they could delete posts?
Not that unlikely, but no more or less likely than if they could use 777 to their advantage.  Think of the database as ALWAYS 777.

  - Doesn't MySQL have permissions?  Can't I make it so they can't delete?
The forum won't work if you do that.  It needs to be able to delete.  If it can delete, so can the hacker.  Dillema, huh?

  - I believe you, but my host doesn't.  They don't want me to make everything 777, they say it's not safe.
So have them read this.  If they can't refute it, prove it wrong, or at least even challenge it then I guess they have to let you do 777 ;D.

  - Even if 777 isn't a problem, why should I bother?
Because it makes things, like for example the package manager and attachments, work better.

Any other questions? (so far I made all these up, sorry if they aren't realistic .)  Feel free to ask and I'll answer away.  I challenge you to prove me wrong.... show me that somehow 777 is all that bad.

- [Unknown]

Znaci i ti nalazis slicne razgovore