Personal computing discussed
Moderators: renee, Steel, notfred
just brew it! wrote:I can't think of any good reason for them to restrict the listen port option. You may still need to hand-cruft the config file to do it though.
Captain Ned wrote:just brew it! wrote:I can't think of any good reason for them to restrict the listen port option. You may still need to hand-cruft the config file to do it though.
Because PuTTY is sending on port 22 to the SSH daemon running on the home box and it's being blocked. Launching PuTTY on port 22 leads to an instant crash back to the desktop with a "connection refused" error message. Launching PuTTY on port 443 doesn't crash but also doesn't connect because the home box isn't listening on 443, so I need to get the daemon on the home box listening on 443.
just brew it! wrote:Note that the trick of running SSH on the "wrong" port may not work, depending on how smart the net nanny box is. I've seen cases where the connection comes up, but then gets cut after a few seconds when the nanny box figures out that the traffic doesn't look like the protocol it is expecting on that port.
The OpenSSH client uses low numbered ports for rhosts and rhosts-rsa authentication because the server needs to trust the username provided by the client. To get around this, you can add the below example to your ssh_config or ~/.ssh/config file.
UsePrivilegedPort no
Or you can specify this option on the command line, using the -o option to ssh(1) command.
$ ssh -o "UsePrivilegedPort no" host.com
DancinJack wrote:Don't know if this is what you are looking for:The OpenSSH client uses low numbered ports for rhosts and rhosts-rsa authentication because the server needs to trust the username provided by the client. To get around this, you can add the below example to your ssh_config or ~/.ssh/config file.
UsePrivilegedPort no
Or you can specify this option on the command line, using the -o option to ssh(1) command.
$ ssh -o "UsePrivilegedPort no" host.com
Think this might be for the full cygwin install on Windows. I've never run the "lite" version. In college they taught us to program from command line in Linux and cygwin was the only way you could do it on a Windows box.
DancinJack wrote:Whoops. I need to know more about this lite version (and SSH in general it appears).
DancinJack wrote:Did you change the port in the sshd_config file?
Steel wrote:Have you checked your home router to see if it can forward SSH traffic to another external port? I have it set up that way on mine, mainly to prevent break in attempts by bots.
Captain Ned wrote:Krep, no go. Damn nanny box is protocol-aware. We'll try a last-ditch attempt tomorrow on port 80.
SecretSquirrel wrote:Captain Ned wrote:Krep, no go. Damn nanny box is protocol-aware. We'll try a last-ditch attempt tomorrow on port 80.
Might also try 81 or whatever port it uses to pass SSL traffic.
--SS
Captain Ned wrote:SecretSquirrel wrote:Captain Ned wrote:Krep, no go. Damn nanny box is protocol-aware. We'll try a last-ditch attempt tomorrow on port 80.
Might also try 81 or whatever port it uses to pass SSL traffic.
--SS
That was my port 443 test this AM.
SecretSquirrel wrote:Are you using proper tunneling software, or just trying to SSH through from your work system to your home system? The latter almost certainly won't work as most corp firewalls block all non HTTP traffic from non-authorized machines. I know ours does. I can't remember the name of the tunnel app I use, but I'll try and dig it up when I get to work tomorrow.
Captain Ned wrote:DancinJack wrote:Whoops. I need to know more about this lite version (and SSH in general it appears).
http://sshwindows.sourceforge.net/
Captain Ned wrote:Success!! And on 443. Things work better when the check box activating the port forwarding rule is actually checked.
just brew it! wrote:D'oh!