SSH client

Good morning,

Is there an SSH client for OS4.1? Something like the old AmTelnet would be good.

@slcroucher

This one works well enough for me:
http://os4depot.net/index.php?functio ... =network/misc/openssh.lha

It's a bit basic looking and uses the CON: device. Is there nothing prettier? Would my old copy of AmTelnet just work?

Wasn't the limitation in AmTelnet ssh v1? It may also need textinput.mcc 27.1 or just some old version.

@Thematic

<blockquote>Wasn't the limitation in AmTelnet ssh v1? It may also need textinput.mcc 27.1 or just some old version.</blockquote>

Yes, AmTelnet quit working for me when my ISP changed to ssh v2.

Yes, I remember now: when I upgraded my linux server by default it had ssh v1 disabled which killed AmTelnet. I seem to remember that was when I switched my A4000 off for the last time.

Can I change the colour of just the newshell window without changing other default colours?

the openssh port is a bit flawed too.. it looks for /home/ and stuff which normally don't exist under aos4 resulting in annoying requesters.

putty would be nice. maybe someone can tackle qputty now as we have qt.

http://qputty.sourceforge.net/

@spotUP
Quote:
That is a feature and not a flaw. I did the OpenSSH port and I decided to use a HOME: assignment so that your private keys are not put someplace you don't expect. I consider security more important than convenience in this case.

edit: see bellow...

ssolie: i am not gonna argue this with you, we have done that long enough. there must be a more elegant way to do it though.

@Steven
Quote:

As amigaos have no security at all , there no point to worry about HOME or whatever for keys, and PROGDIR: instead can be used with no problems (i.e. have keys in the root of unpacked openssh). Like PROGDIR:.keys/ or something.

Because currently its really make no sense to have HOME if it all only about security which aos didn't have.

And i must to say, what i do not expect, its to have my keys in /home/ on amigaos, but i expect them to be in PROGDIR: , of course.

@spotUP & all,

I found the HOME global variable and a few other things
should be set in your User-StartUp for SSH to work best.

Just add and edit these lines as needed:

;BEGIN SSH
path <PATH TO YOUR SSH INSTALL DIR> ADD
setenv HOME Internet:OpenSSH/
setenv USER <YOUR ACCOUNT'S USER NAME>
setenv TERM amiga-8bit
;END SSH

Good luck,

PJS

@Pjs
Yeah, i use about the same :)

Quote:

Which is in general the same usual PROGDIR:, which imho ssh itself can use instead of HOME.

kasie, indeed.

@pjs

Don't add a ssh specific HOME assign else you will get other programs dumping there stuff in there,

eg abc-shell , cvs, svn and an number of other unix ports.

Justmake a sys:home or work:home or whereever you want it and assign HOME: to that.

@kas1e

You should *not* use progdir for programs like ssh wich are likely to endup in C:

@Andy
Then maybe it should be something like dunno, PREFS:ENV/.sshkeys, or dunno .. in other words more amiga like, not /HOME/

@kas1e

perhaps, you can always do assign HOME: ENVARC: or something.

@broadblues

It's not an assign it needs. At least, here, I have an env-var HOME (and, yes, it points to ENVARC:, which seems to be the most logical place)