still no ssh access

Brian Kelsay Brian.Kelsay at kcc.usda.gov
Fri Oct 1 09:57:05 CDT 2004


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





More information about the Kclug mailing list