Re: ssh or equivalent on lispm/macivory

[email protected] wrote:
> I've got a MacIvory 2 and a couple of 3640s.  Having them networked
> together is fairly straight-forward.  Unfortunately, if I want that
> network to be connected to anything other than Lisp machines living
> within my house, they can only use encrypted means for user data
> communication.  I.e., DNS and such can still be in the clear, but
> remote logins, X sessions, file transfers, etc, have to be encrypted.
> The existing infrastructure is very much geared to ssh, but that's not
> a strict requirement.
> 

For an occasional use, you could set up a box on your local network that does 
port forwarding.  I don't know what MacOS you've got on the MacIvory, but there 
are versions of SSH on the Mac.  Alternatively, you could add a, say, Linux box 
running a version of SSH.   Then you set up the ssh to tunnel the communications 
to a particular other end.  For instance, you start up the ssh on the Mac or 
Linux box so it is ssh'ing to Remote-Host.  Then you can tell the ssh machine 
that connections to its Telnet port should be tunneled to the telnet port on 
Remote-Host.  From the Lispm, you telnet to the local ssh host and you will find 
yourself prompted to login to the Remote-Host.

[This is what happens to packets:  Your Lispm sends a packet to Local-ssh-host 
(to port 23, from port, say, 1025).  Local-ssh-host sends that packet 
(encrypted) along its ssh-encrypted link to Remote-ssh-host.  The sshd at the 
Remote-ssh-host sends that unencrypted packet to the telnet port on Remote-Host 
(to port 23, from port, say, 1933).  Remote-Host thinks you are coming in from 
Remote-ssh-host.  (NOTE: Remote-Host and Remote-ssh-host can be the same host) 
Remote-Host sends its (unencrypted) response packet back to Remote-ssh-host (to 
port 1933, from port 23).  The sshd on Remote-ssh-host sends the packet 
(encrypted) back to Local-ssh-host.  Local-ssh-host then sends the unencrypted 
packet to Lispm (to port 1025, from port 23).]

X windows works ok, but will be slow.  FTP is more problematic.  For more 
details, poke around port-forwarding in the docs on various ssh versions.

Another way is to get VPN hardware.

SSH for the Mac:

Niftytelnet w/ssh (has scp -- secure file transfer)
    http://www.lysator.liu.se/~jonasw/freeware/
   http://asg.web.cmu.edu/andrew2/dist/niftytelnet.html
   I don't know if it can do port forwarding.  Apparently runs in MacOS 7.x and 
newer.

MacSSH
   http://www.macssh.com
   FAQ & pointer to port forwarding info:
      http://pro.wanadoo.fr/chombier/FAQ.html
    May only run in 8.1 and newer

F-Secure
   Commercial brand.  $115
   http://www.fsecure.com/
   Does do port forwarding. MacOS 7.5.5 or later.


Of course, there's no reason you couldn't write your own ssh for Genera!
But maybe someone has already.