On Tue, 20 Jun 2000, Mike Friedman wrote:
> On Tue Jun 20 09:35:05 2000, Tin Le said:
> > There is at least another situation where it does make sense to run sshd
> > under inetd, besides the one you mentioned.
> >
> > That is where the box is in a location far away (physically) and you want
> > to make sure that if the (OS)network layer works, you can access it via
> > ssh.
> What many people (including me) do is run a 'backup' sshd at a non-standard
> port out of inetd, for use just when the standalone sshd has failed. This
> gives you a way to login to restart the regular sshd (or to investigate why
> it won't start!), but the latter would still be what most users normally
> connect to (at the standard port 22).
Funny enough, I have similar setup on my home machine. It's just that
I have not had a need for the remote server till now. Plus I try not to
make changes to it, as it is an awful long drive from home.
Another thing I've done is setup a web page to use Mindterm Java applet
to allow me to come in via a hidden and protected web page. Works great
for times when I work at a client site with very restrictive firewall, but
I need access to my server. Or when I am traveling and stopping at a web
kiosk to check something on my home machine.
Tin Le
----
http://tin.le.org
Internet Security and Firewall Consulting
Tin Le - [EMAIL PROTECTED]
