KCLUG

1 participants
3235 discussions

RE: apache questions to follow
by Brian Densmore 01 Oct '04

01 Oct '04

make sure there is a line that looks something like this: ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/cgiirc/ This tells apache where to find script directories. (I think that is the correct syntax) Also you'll need a section like this: <Directory /usr/lib/cgi-bin/cgiirc/> AllowOverride None Options ExecCGI Order deny,allow Allow from all </Directory> Make sure to remember the final / on the directory names. I've never used more than one directory for scripts, so I don't know if making the above changes will redirect all cgi requests to the new .../cgiirc directory or not. But unless you tell apache there are scripts there and make the directory ExecCGI, they won't execute. You may need to qualify the path for the scripts so that the cgi requests go to /cgiirc/irc.cgi, if the ScriptAlias is like mine and points to /usr/lib/cgi-bin. Brian Densmore > -----Original Message----- > From: Brian Kelsay > > > revise that, I think it is /usr/lib/cgi-bin/cgiirc > > Brian Kelsay > > >>> "Brian Kelsay" 10/01/04 03:39PM >>> > > The scripts for cgiirc live in /usr/share/cgiirc. > > > > _______________________________________________ > Kclug mailing list > Kclug(a)kclug.org > http://kclug.org/mailman/listinfo/kclug >

3 4

Re: apache questions to follow
by Brian Kelsay 01 Oct '04

01 Oct '04

revise that, I think it is /usr/lib/cgi-bin/cgiirc Brian Kelsay >>> "Brian Kelsay" <Brian.Kelsay> 10/01/04 03:39PM >>> The scripts for cgiirc live in /usr/share/cgiirc.

1 0

apache questions to follow
by Brian Kelsay 01 Oct '04

01 Oct '04

The "Listen" parameter is commented out and the comments say to add IPs to listen to in addition to default. How do I know if the default is set correctly? I've seen a message while trying to access a .cgi file that the server was on 127.0.0.1. To me that seems wrong. As I said, I get an error, "The requested URL /irc.cgi was not found on this server. Apache/1.3.27 Server at 127.0.0.1 Port 80" I've got cgiirc installed via apt, but the cgi script is not working. I've got httpd.conf open, as I assume that cgi is not enabled. I'm trying to find that line now. mod_cgi.so is getting loaded. On the Options line, I added ExecCGI. The scripts for cgiirc live in /usr/share/cgiirc. When I get this fixed, I will hopefully be able to have IRC access from anywhere to #kclug, #knoppix, #debian, #damnsmalllinux, #morphix on freenode. Brian Kelsay

1 0

Re: still no ssh access
by Brian Kelsay 01 Oct '04

01 Oct '04

J Riley gets the golden banana. This gave me the winning combination. Firewall port forward 443 to 22 works and doesn't mess up the webserver access or config. Port 80 still available and I didn't have to do anything to sshd.conf. Brian Kelsay >>> <JARiley> 09/30/04 03:13PM >>> Why don't you just change your sshd config file to use port 443, then the encrypted traffic won't throw up any flags to the firewall admins. James Riley, CISSP

1 0

Re: still no ssh access
by Brian Kelsay 30 Sep '04

30 Sep '04

PPPoE is not a factor as I have Comcast cable not RR. No I haven't tried to connect to the firewall. If I want to, I enable ssh and it defaults to port 222. [OT] On the PPPoE front, my wife wants me to look into/consider switching to SBC DSL, getting phone, internet and cell thru them and then we could get satellite TV. I've got to run the numbers and see if that combo will be cheaper. If I get a TIVO satellite receiver thrown in I may do it. I haven't actually recorded any TV shows in 6-8 months, but w/ TIVO I think I would. Especially if I could get the LAN stuff setup w/ the unit. View the recorded programs on my PC. Brian Kelsay >>> Jonathan Hutchins <> 09/30/04 04:04PM >>> On Thursday 30 September 2004 01:04 pm, Brian Kelsay wrote: > Now that I have sshd running on the new server and I can connect to it from > another PC on my LAN, I know that it should work. Have you tried connecting to the firewall itself with ssh? What kind of WAN connection do you have? I was unable to connect to a system that was on an SBC PPPoE modem. I think the problem was with the PPPoE connection, but I never did track it down.

1 0

still no ssh access
by Brian Kelsay 30 Sep '04

30 Sep '04

Now that I have sshd running on the new server and I can connect to it from another PC on my LAN, I know that it should work. I have setup port 80, 8000 and 21 to forward to 22 on the server, but none allow me to connect with Putty from work. Those that remember, I had narrowed it down to port 80 being unblocked on outbound and POSSIBLY port 21. I just want the ability to sftp a few small files to it, enable new functions and test the webserver in general. The rules are set up in IPCop correctly. I am about to resign myself to the fact that there is no way to do this unless there is some other package that I can put on the server to allow remote access via port 80 or 443 (https). Anybody know of something like webmin that comes by default to work on 443 and then allows you to ssh or ftp? I feel really stupid. The next step I will try is to put webmin on 443 instead of 10000 or whatever it is set by default, but I'm not confident. I probably need to leave my current port forwarding rules until LUG meeting night to see if I can get in remotely from another location. This has been a testing nightmare for me. Brian Kelsay

5 4

Re: still no ssh access
by Brian Kelsay 30 Sep '04

30 Sep '04

Now that is a good question and probably the answer. I believe in the scientific method for testing of any type. Make changes to only one item at a time until all are exhausted so you know what made the difference. I have never had to change this before. I assume it is sshd.conf. I'll give it a look tonight and set everything else back the way it was. Brian Kelsay >>> <JARiley 09/30/04 03:13PM >>> Why don't you just change your sshd config file to use port 443, then the encrypted traffic won't throw up any flags to the firewall admins. James Riley, CISSP

1 0

Re: still no ssh access
by Brian Kelsay 30 Sep '04

30 Sep '04

Interesting, but I have already been able to use Putty on a PC in my LAN. It worked with no change. Brian Kelsay >>> Rich Edelman <redelman(a)speedscript.com> 09/30/04 01:39PM >>> What I've found I needed to do to allow PuTTY and WinSCP clients to connect is to change the sshd config. These are the options I needed to change, keep in mind this has been on SuSE 9.x, your distribution may vary. /etc/ssh/sshd_config: #PasswordAuthentication no #PermitEmptyPasswords no UsePAM yes

2 1

RE: still no ssh access
by Brian Kelsay 30 Sep '04

30 Sep '04

The IPCop box, if ssh is enabled on it, will allow ssh on 222. You can then port forward 22 to one box internal and setup any others with different external ports forwarded to specific boxes port 22. e.g. ip:22 -->192.168.0.3:22, ip:1022-->192.168.0.4:22, ip:1023-->192.168.0.5:22. Unfortuantely I can't do that. My workplace blocks outbound connections to anything but 80, 443 and 21 (ftp). I have tried port 22, 80, and 21 forwarded at the firewall to server port 22. Brian Kelsay >>> "Dustin Decker" <dustin.decker(a)1on1security.com> 09/30/04 01:25PM >>> IPCop is designed to have ssh run on port 222, leaving you the luxury of forwarding the SSH port (which is 22 btw, not 21) to another host on your network. If you're on RoadRunner, you might want to modify IPCop to have the web admin interface listen on something other than port 445, as that is blocked because of the number of worms which attack Win2K on that port. If you are trying to connect to a host _behind_ IPCop, forward port 22 to that host. If you are trying to connect to IPCol itself, use the -p flag to connect on port 222. Dustin > -----Original Message----- > Of Brian Kelsay > Sent: Thursday, September 30, 2004 1:04 PM > To: kclug(a)kclug.org > Subject: still no ssh access > > Now that I have sshd running on the new server and I can connect to it > from another PC on my LAN, I know that it should work. I have setup port > 80, 8000 and 21 to forward to 22 on the server, but none allow me to > connect with Putty from work. Those that remember, I had narrowed it down > to port 80 being unblocked on outbound and POSSIBLY port 21. I just want > the ability to sftp a few small files to it, enable new functions and test > the webserver in general. The rules are set up in IPCop correctly. I am > about to resign myself to the fact that there is no way to do this unless > there is some other package that I can put on the server to allow remote > access via port 80 or 443 (https). > > Anybody know of something like webmin that comes by default to work on 443 > and then allows you to ssh or ftp? I feel really stupid. The next step > I will try is to put webmin on 443 instead of 10000 or whatever it is set > by default, but I'm not confident. > > I probably need to leave my current port forwarding rules until LUG > meeting night to see if I can get in remotely from another location. > This has been a testing nightmare for me. > > Brian Kelsay

1 0

Re: still no ssh access
by Brian Kelsay 30 Sep '04

30 Sep '04

Why should it matter? It is not 3 services, but one, with one ultimate destination and I am the only user. There are no connections on 22, 80, 21 or 8000 until I attempt them. I only attempt to connect to one at a time. What's the difference from this and having a firewall forward both 80 and 8080 to the same webserver, which I understand is standard practice? Brian Kelsay >>> crash 3m <crash3m(a)gmail.com> 09/30/04 01:22PM >>> Your forwarding 3 ports, to 1 port? I dont believe thats a workable solution, if you forward port 80 on the external machine, to 22 on the internal machine, and set putty to connect to port 80 for an ssh/scp connection you can transfer your files. But AFAIK (and IANA tcpi/ip expert) you cannot have the 3 services listening on the same port on the same protocol (e.g. you could have one on udp and one on tcp) Surely there will be some others that will chime in with a more accurate answer. On Thu, 30 Sep 2004 13:04:01 -0500, Brian Kelsay <brian.kelsay(a)kcc.usda.gov> wrote: > Now that I have sshd running on the new server and I can connect to it from another PC on my LAN, I know that it should work. I have setup port 80, 8000 and 21 to forward to 22 on the server, but none allow me to connect with Putty from work. Those that remember, I had narrowed it down to port 80 being unblocked on outbound and POSSIBLY port 21. I just want the ability to sftp a few small files to it, enable new functions and test the webserver in general. The rules are set up in IPCop correctly. I am about to resign myself to the fact that there is no way to do this unless there is some other package that I can put on the server to allow remote access via port 80 or 443 (https). > > Anybody know of something like webmin that comes by default to work on 443 and then allows you to ssh or ftp? I feel really stupid. The next step I will try is to put webmin on 443 instead of 10000 or whatever it is set by default, but I'm not confident. > > I probably need to leave my current port forwarding rules until LUG meeting night to see if I can get in remotely from another location. This has been a testing nightmare for me. > > Brian Kelsay > > _______________________________________________ > Kclug mailing list > Kclug(a)kclug.org > http://kclug.org/mailman/listinfo/kclug > -- Got gmail? I do hahaha _______________________________________________ Kclug mailing list Kclug(a)kclug.org http://kclug.org/mailman/listinfo/kclug

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

KCLUG