[179036] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Frontier: Blocking port 22 because of illegal files?

daemon@ATHENA.MIT.EDU (Jens Link)
Thu Mar 26 08:10:44 2015

X-Original-To: nanog@nanog.org
From: Jens Link <lists@quux.de>
To: nanog@nanog.org
Date: Thu, 26 Mar 2015 13:10:35 +0100
In-Reply-To: <5513EC76.5060306@satchell.net> (Stephen Satchell's message of
 "Thu, 26 Mar 2015 04:24:38 -0700")
Errors-To: nanog-bounces@nanog.org

Stephen Satchell <list@satchell.net> writes:

> It's been a while since I did this, but you can select an additional
> port to accept SSH connections.  

That's easy: 

jens@screen:~$ grep Port /etc/ssh/sshd_config  
Port 22
Port 443
 
> Picking the right port to use is an exercise, though, that will depend
> on what other services you are running on your server.

I always have at least one sshd listening on port 443. For all the
hotel, coffee house, customer networks blocking ssh.  

You can even multiplex and run ssh and ssl on the same port:

http://www.rutschle.net/tech/sslh.shtml

Jens
-- 
----------------------------------------------------------------------------
| Foelderichstr. 40   | 13595 Berlin, Germany           | +49-151-18721264 |
| http://blog.quux.de | jabber: jenslink@jabber.quux.de | ---------------  | 
----------------------------------------------------------------------------

home help back first fref pref prev next nref lref last post