Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I know that one should avoid setting file/folder permissions to 777 and instead use a more granular approach.

I would like to know, if there are specific cases when using chmod 777 on a webserver is justified.

share|improve this question

closed as not a real question by Bill Weiss, EightBitTony, voretaq7 Jul 24 '12 at 15:40

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
chmod 777 on what? i.e. a directory in the web server path, or somewhere else. Without a specific example, the only possible answer is one of 'maybe' or 'possibly' or 'probably'. –  EightBitTony Jun 6 '12 at 11:31
2  
In which situation are you really interested? There are going to be different answers depending on what environment you're in (corporate, small business, public facing server, personal VM, etc). –  squillman Jun 6 '12 at 11:38
2  
If you are struggling to find valid cases, then surely you've already answered your question –  symcbean Jun 6 '12 at 12:11
add comment

1 Answer

up vote 4 down vote accepted

No. There are always ways to tighten up permissions appropriately.

share|improve this answer
2  
If you have a directory to which everyone in the universe genuinely needs full access, then 777 is justified. I think it's naive to say it's never required. Sure, it should be unusual and by exception only, but it's not inconceivable. –  EightBitTony Jun 6 '12 at 11:32
1  
On a web server? Again, better ways. –  Ignacio Vazquez-Abrams Jun 6 '12 at 11:35
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.