Hi robert, thanks for the replies the other day on the apache help message. I had to do a complete install from scratch to get apache working like you did. it works here at work but not at home so I guess another install
I would like to see SuSE change the default /etc/httpd/httpd.conf from "-FollowSymLinks" to "+FollowSymLinks". This would help a lot of users. Is there a good reason why it's not +FollowSymLinks as a default ? /Dee -----Original Message----- From: Robert C. Paulsen Jr. [mailto:paulsen@texas.net] Sent: Friday, June 29, 2001 10:09 AM To: Jack Malone Cc: Robert C. Paulsen Jr.; suse-linux-e@suse.com Subject: Re: [SLE] apache On Fri, Jun 29, 2001 at 12:34:35PM -0500, Jack Malone wrote: there.
another question now do you know what I need to do to make say /home/jack/public_html readible now . i have gone an done a chmod o+x /home/jack an also chmod o+r /home/jack/public_html an still can not pull the page there from a windows machine. I can enter the ip address of hte suse box an get the default suse test info page. Am I doing something wrong here or what. I had this working once in the past an now I forgot what I did to make it work. thanks for any info.
Three things I can think of right now: First: You have might not have the permissions right. What you describe above looks like it should be OK, but check to make sure. Here is an ls -l of my directories:
ls -ld /home/robert drwxr-xr-x 54 robert users 4096 Jun 29 12:53 /home/robert/
ls -ld /home/robert/public_html drwxr-xr-x 12 robert users 4096 Jun 28 08:46 /home/robert/public_html/
ls -l /home/robert/public_html/index.html -rw-r--r-- 1 robert users 8801 Dec 31 18:31 /home/robert/public_html/index.html
Second, On SuSE, Apache is configured by default to not follow symbolic links. If /home or /home/jack etc. is a symbolic link it will not work. There is an option ("-FollowSymLinks") in httpd.conf that you can change to "+FollowSymLinks". Third: You might have messed up your httpd.conf. Compare with the one from your working setup. -- ____________________________________________________________________ Robert Paulsen paulsen@texas.net
* Dee McKinney
I would like to see SuSE change the default /etc/httpd/httpd.conf from "-FollowSymLinks" to "+FollowSymLinks". This would help a lot of users.
Is there a good reason why it's not +FollowSymLinks as a default ?
Security reasons. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On June 29, 2001 04:40 pm, Dee McKinney wrote:
I would like to see SuSE change the default /etc/httpd/httpd.conf from "-FollowSymLinks" to "+FollowSymLinks". This would help a lot of users.
Is there a good reason why it's not +FollowSymLinks as a default ?
Absolutely. You probably let web authors create files under your htdocs directory or their public_html directories. Imagine if one created a symlink to /etc or something. Your anonymous FTP server is set up in the same way. I'm glad that the secure option is default in SuSE. If you don't care about the security issues, you can change it yourself. It is better that the user knows the issue if they are vulnerable. - -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7PNyL+FOexA3koIgRAvQJAJ9d7tY6q1uzj2Uj6VnodeWbY19GQwCffySf 0hjsOqKwwZtzY/yX6lRV2RU= =s02S -----END PGP SIGNATURE-----
Ok but does anyone else beside Robert have any comments on my problem from the original context of this message. I'm stumped at the moment, I can not recreate a working situation again for the life of me had it working back in 7.1 before I upgraded that machine at home an messed it up thanks if need be i will repost the original message again. thanks jack At 04:52 PM 6/29/2001 -0300, James Oakley wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On June 29, 2001 04:40 pm, Dee McKinney wrote:
I would like to see SuSE change the default /etc/httpd/httpd.conf from "-FollowSymLinks" to "+FollowSymLinks". This would help a lot of users.
Is there a good reason why it's not +FollowSymLinks as a default ?
Absolutely. You probably let web authors create files under your htdocs directory or their public_html directories. Imagine if one created a symlink to /etc or something.
Your anonymous FTP server is set up in the same way.
I'm glad that the secure option is default in SuSE. If you don't care about the security issues, you can change it yourself. It is better that the user knows the issue if they are vulnerable.
- -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE7PNyL+FOexA3koIgRAvQJAJ9d7tY6q1uzj2Uj6VnodeWbY19GQwCffySf 0hjsOqKwwZtzY/yX6lRV2RU= =s02S -----END PGP SIGNATURE-----
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
* Jack Malone
Ok but does anyone else beside Robert have any comments on my problem from the original context of this message. I'm stumped at the moment, I can not recreate a working situation again for the life of me had it working back in 7.1 before I upgraded that machine at home an messed it up
OUPS -- please don't Cc: feedback@suse.de when posting to this list. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
I dont know if you saw this the other day but I had a similar problem [for the benifit of those who care] Responding to my own question here... ######################################### I got the perm info below from the SuSE unleashed book, apparently the permssions are not adequate.
chown -R USERNAME.nogroup ~USERNAME/public_html chmod -R 2777 ~USERNAME/public_html
I had to chmod -R 711 ~USERNAME and then chmod -R 755 public_html ############################################ that worked for me rob Jack Malone wrote:
Ok but does anyone else beside Robert have any comments on my problem from the original context of this message. I'm stumped at the moment, I can not recreate a working situation again for the life of me had it working back in 7.1 before I upgraded that machine at home an messed it up
thanks if need be i will repost the original message again.
thanks jack
At 04:52 PM 6/29/2001 -0300, James Oakley wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On June 29, 2001 04:40 pm, Dee McKinney wrote:
I would like to see SuSE change the default /etc/httpd/httpd.conf from "-FollowSymLinks" to "+FollowSymLinks". This would help a lot of users.
Is there a good reason why it's not +FollowSymLinks as a default ?
Absolutely. You probably let web authors create files under your htdocs directory or their public_html directories. Imagine if one created a symlink to /etc or something.
Your anonymous FTP server is set up in the same way.
I'm glad that the secure option is default in SuSE. If you don't care about the security issues, you can change it yourself. It is better that the user knows the issue if they are vulnerable.
- -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE7PNyL+FOexA3koIgRAvQJAJ9d7tY6q1uzj2Uj6VnodeWbY19GQwCffySf 0hjsOqKwwZtzY/yX6lRV2RU= =s02S -----END PGP SIGNATURE-----
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- Linux Off Topic Discussion Send a blank email to mailto:lx-talk-subscribe@big7.net
I opted for a clean 7.2 rebuild of our server. Using SuSE 6.4, this computer served as Internet masq, printer server, ssh2 server, etc for a small Mac/Win art shop. I choose minimum install and added SuSEfirewall. I got it to work once, but then foolishly decided to go for that "killer clean install", after having experimented with many various settings. Well, I have not gotten it to work since, and I'm pretty sure I used the basic settings as in the manual when it did work. It seemed so easy! eth0 24.4.x.x @home cable connection with static IP eth1 192.168.1.100 internal network Everybody can ping each other: ifconfig looks decent enough based on what I know (I'm graphics/video/network admin... so, discount my admin skills mightily). 24.4.x.x 24.4.126.129 my gateway 192.168.1.10 my w2k Athlon 192.168.1.51 my Mac Powerbook 500 No masq from my internal machines. They point to 192.168.1.100 as gateway and are using the same configuration as on the previous year-long running server. ---- Clean install, minimum + SuSEfirewall set-up ethernet cards, check ping and ifconfig edit rc.config to turn on IP forwarding edit /etc/rc.config.d/firewall.rc.config FW_DEVWORLD eth0 FW_DEV_INT eth1 FW_ROUTE yes FW_MASQUERADE yes FW_MASQ_NETS 192.168.1.0/24" reboot ---- I have also tried leaving FW_MASQ_NETS empty entering FW_MASQ_NETS 192.168.1.0/8" entering FW_MASQ_NETS 192.168.0.0/24" I don't really understand the netmask variation, but seems like one of those should work. How can I further troubleshoot this? Thanks!
participants (6)
-
Daniel Woodard -
Dee McKinney -
dizzy -
Jack Malone -
James Oakley -
Mads Martin Jørgensen