Re: [TCLUG:16456] X on a Remote Server

[Chris McKinley <lamfada@lugh.net>]

I think I did, however your problem would be solved by installing
ssh1 / OpenSSH at home and compiling ssh2 with ssh1 compatability,
thus, you should never, ever need telnet.

Blarg!

-Chris

On Thu, 20 Apr 2000 Nick.T.Reinking@supervalu.com wrote:

> I think you missed what I mean.
> 
> If I'm at work, that means I'm using ssh1 (not ssh2 - license).
> But if it is my home machine (educational?) - ssh2
> Therefore I can't connect, so I have to run telnet.
> 
> I was being sarcastic, bloog!
> 
> We all should be running ssh1 everywhere.  Down with ssh2!
> 
> Nick Reinking
> 
> 
> 
> 
> 
> lamfada@lugh.net, on 04/20/2000 02:30:15 PM
> To: tclug-list@mn-linux.org @ PMDF
> cc:  
> Subject: Re: [TCLUG:16456] X on a Remote Server
> 
> 
> On Thu, 20 Apr 2000 Nick.T.Reinking@supervalu.com wrote:
> 
> > Most of us on the list would like to use ssh at the places that
> > we work, also.  ;)  I guess we can all just use rsh and telnet at
> > work, it's always good having a few big security holes about,
> > makes things interesting.  (We can also leave open telnet on
> > our machines at home, too?)
> 
> Or why not just run ssh on port 23? Or use ipchains to port forward
> 23->22?
> 
> -Chris
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> For additional commands, e-mail: tclug-list-help@mn-linux.org
> 
> 
> 
> 
>