I would be VERY HIGHLY wary of setting write permision for *anyone* expect root to the / partition, most especially so people can "view something on your computer through the internet".
You seem not to understand exactly what is required to do that! Do they have accounts on your machine? if so, what's the problem?
You are confusing / - the root partition on your HD, with "/" - the root partition of your html docs.
Find the apache config files. in there it will specify something like htdocs/htdoc or something. That's the root of your html files. The problem is likely that *this* directory, your htdoc root dir, is not 755 like it should be.
I already set the config file to open my website folder(/root/mywebsite) and when i try to go to my website i get that error? I set the file permissions on /root and /root/mywebsite and the HTML file containing my website to be able to be read but it did nothing?
you set read permissions for the directories? well that's your first problem. This is such a fundamental part of the OS that you really should understand it.
Read this:
http://www.freeos.com/articles/3127/
and then read the manpage for chmod(1) - do a "man chmod" at an xterm. Read this (it's pretty short).
For webpages served by apache, you need to set the "all" permissions since the owner of the apache process (PLEASE tell me it's not root!!!!) is unlikely to be either the owner of, or in the group of the htdocs dir. 755 for dirs, 644 for files.
errr...*YES*!! Running services like this, especially network ones, as root is a VERY bad idea unless there is a very compelling reason not to. I can't think of a reason to run httpd as root. I thought the default was even to run as a completely unprivelledged account, like using the "nobody" or "daemon" account or something.
General rule of thumb: The less root processes you have running, the more resillient your system will be to attacks. And you *will* be attacked! I've seen machine compromised in less than 5 minutes of being brought up on the internet. A web server is certainly a weak point...
Agent Orange
203 Posts
0
May 23rd, 2004 16:00
e.g. $ chmod 755 /
I would be VERY HIGHLY wary of setting write permision for *anyone* expect root to the / partition, most especially so people can "view something on your computer through the internet".
You seem not to understand exactly what is required to do that! Do they have accounts on your machine? if so, what's the problem?
cheers
HALO PRO
2 Intern
•
357 Posts
0
May 24th, 2004 06:00
Message Edited by HALO PRO on 05-24-2004 03:20 AM
Agent Orange
203 Posts
0
May 24th, 2004 09:00
You are confusing / - the root partition on your HD, with "/" - the root partition of your html docs.
Find the apache config files. in there it will specify something like htdocs/htdoc or something. That's the root of your html files. The problem is likely that *this* directory, your htdoc root dir, is not 755 like it should be.
cheers
HALO PRO
2 Intern
•
357 Posts
0
May 24th, 2004 20:00
Agent Orange
203 Posts
0
May 25th, 2004 07:00
HALO PRO
2 Intern
•
357 Posts
0
May 25th, 2004 07:00
Agent Orange
203 Posts
0
May 25th, 2004 12:00
Read this:
http://www.freeos.com/articles/3127/
and then read the manpage for chmod(1) - do a "man chmod" at an xterm. Read this (it's pretty short).
For webpages served by apache, you need to set the "all" permissions since the owner of the apache process (PLEASE tell me it's not root!!!!) is unlikely to be either the owner of, or in the group of the htdocs dir. 755 for dirs, 644 for files.
HALO PRO
2 Intern
•
357 Posts
0
May 25th, 2004 22:00
" (PLEASE tell me it's not root!!!!) "
So your saying i should manage it under another username and not root?
Agent Orange
203 Posts
0
May 26th, 2004 11:00
General rule of thumb: The less root processes you have running, the more resillient your system will be to attacks. And you *will* be attacked! I've seen machine compromised in less than 5 minutes of being brought up on the internet. A web server is certainly a weak point...
cheers
HALO PRO
2 Intern
•
357 Posts
0
May 26th, 2004 20:00