Apache: difference between chmod 644 and chmod 666 and chmod 600 for output/txt/dat?
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Apache: difference between chmod 644 and chmod 666 and chmod 600 for output/txt/dat?
Hello,
What is the difference between chmod 644 and chmod 666 and chmod 600 for output/txt/dat on website/apache server?
Little confused, in terms of security, and for board / messages... ?
Quote:
Permissions
u - User who owns the file.
g - Group that owns the file.
o - Other.
a - All.
r - Read the file.
w - Write or edit the file.
x - Execute or run the file as a program.
Numeric Permissions:
CHMOD can also to attributed by using Numeric Permissions:
400 read by owner
040 read by group
004 read by anybody (other)
200 write by owner
020 write by group
002 write by anybody
100 execute by owner
010 execute by group
001 execute by anybody
Well, the web-server is the owner of the file then, and then only the first digit matters.
I still dont understnd why people want something un-secured,
I quote this:
Quote:
5. Make sure file test.txt inside "logs" folder is writable by PHP scripts. On Unix (Linux) servers CHMOD this file to 666 (rw-rw-rw-).
That's it. To test if PHPGCounte works fine open graphcount.php?page=test in your browser, for example:
Well, that's a different question. Usually www-data does not have many privileges, while other accounts on a web server have a lot more. So preventing e.g. you to read/write the file, does not add much to security. You could of course chown, then chmod it 600, but that's more like securing the web server from you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.