[rescue] SGI fw_sshd and security

Kevin kevin at mpcf.com
Fri Mar 5 15:15:02 CST 2004

In my previous experience, ssh is fine on ports other than 22
with Slackware, slack, like almost all linux distros uses
opensshd just as IRIX does, so you won't find any
incompatibilities there.  It's not a compile time option or

As for WinXP, every ssh client i've used under Windows could
(and did) work on ports other than 22.

If you are really concerned you might try an iptables/linux
firewall and implement port knocking.  Google port knocking if
you're unfamiliar with it.  Very interesting security method,
little bit of a PITA on the client side but doable nonetheless.


On Fri, 5 Mar 2004 14:06:44 -0500
"Sheldon T. Hall" <shel at cmhcsys.com> wrote:

> Gary Nichols says ...
> > You should really run SSH on another port besides 22 and
> > consider using shared keys on both sides along with password
> > authentication.
> How's the compatibility with various clients when you use
> other-than-22?  My son and I might be using ...
> 	slackware linux on a PC
> 	WinXP on a PC (does it even have an ssh client?)
> 	Cygwin on Win2K on a PC

More information about the rescue mailing list