4

With a new purchase coming in shortly I wanted to ask what do I need to be able to SSH to a remote host from an Amiga:

  1. Make modem work and connect to my network:
    https://www.ebay.com/itm/KCWIFI-PRO-c64-plus4-c128-Amiga-Apple-II-PET-retro-rs232-modem-wifi-hayes-AT/154303064959?hash=item23ed2deb7f:g:4F8AAOSwfrleChLb
  2. Install SSH client:
    http://amiga.sourceforge.net/?showpackage=OpenSSH
  3. Configure? What how?

Seems like a daunting task considering I never done it before, but is my thinking correct? Did I miss anything or is there any gotchas to bear in mind?

3
  • 1
    I don't have experience with Amiga, but I've set up an SSH client on a DOS retro-machine and that looks right as long as the Amiga version of OpenSSH is modern enough to support one of the ciphers still on the SSH server's allowed list. (Like SSL/TLS, SSH prefs off ciphers as they become "no longer considered secure enough".) If it's anything like the Linux and DOS SSH clients, and the default ciphers on the server are OK, and you haven't restricted it to pubkey auth only on the server, then it should Just Work™ with no step 3. – ssokolow Mar 21 at 19:02
  • 2
    If you find that you cannot make the Amiga connect directly to a host using ssh, or it may be too slow, you might consider having a small Linux box which the Amiga can telnet to, and then ssh from that box onwards. Seen from the users point of view telnet and ssh are very similar. – Thorbjørn Ravn Andersen Mar 22 at 0:49
  • The SSH packages listed behind the link are severely outdated: 3.7 3.8 3.9, dated 2003 and 2004. So outdated that they might not have common cipher (cf. @ssokolow comment) and/or moot security because of known bugs, see e.g. cvedetails.com/… – Stéphane Gourichon Jun 1 at 19:20
5

One thing you will certainly need: Patience, a lot of it. Establishing SSH connections with either the client or server side having a very low performance CPU (as in, an 68xxx. I once tried with the client on a Mac LCII with NetBSD...) can take several MINUTES to do all the key exchange work. Also, plan in half an hour for generating the keys when installing an SSH server on such a machine...

Since this probably on a network behind some kind of perimeter firewall (eg your DSL router) and for experimental/personal use - do feel justified to ignore best practices and use an unencrypted (telnet, rlogin, rsh...) connection for shell access.

2

For configuration of SANA-II drivers for serial line interfaces see Roadshow, "slip.device" is your friend. Better use a newer openssl port because the encryption methods may be obsolete.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.