SSHTerm "Authentication password failed" (SOLVED)

On my X1000 this works fine, but on my X5000 SSHTerm refuses to connect.

I have downloaded the latest SSHTerm. I have copied over those file to my Programs partition. I have added a "HOME" assign to Workbench:S, I have created a .ssh folder in there.

I run something like: "sshterm 4.4.4.4 myUserName", I got a prompt to enter my password. I enter the correct password and then I get, to stdout/stderr: "Authentication password failed".

I have also the latest AMISSL installed.

=== edit
BTW, I can log into my machines using ssh/Openssh without any problems.

@rjd324

Try specifying the password from the command line.

If it works that way then you are encountering one of the race condition bugs that exists in the latest public version of string.gadget, but should be fixed in the latest beta version.

@salass00

I can confirm that entering the password as an argument directly works.

Solution: Wait for an update to "string.gadget"

I will mark it as solved.

For reference, the current version of string.gadget for me is (the one that is apparently causing the issue):

Hmm, I am not convinced that it is string.gadget that is causing the issue. I just happened to check the two versions on my X1000 and my X5000 and they are both the same. I can log in using the X1000.

Is anyone able to login using the SSHTerm popup password box?

@rjd324

Since it seems to be a race condition, the difference in speed etc. between your two machines and (maybe especially) their graphics cards will very likely be a factor in whether it appears or not.

Which graphics cards do you have in the two machines?

Best regards,

Niels

I use rx560 in the x5 and hd7950 in the x1.

@rjd324
I had a similar problem with my X 5000
Add the following line at your user-startup and see if that helps.

Sys:Prefs/Power QUIET

Please adjust if you have the Power prefs in an other place.

@rjd324

SSL you have libssl.a that is compiled into the program, using static linking at compile time.
There is libssl.so file that can be linked at runtime using dynamic linking.
And then there is openssl.library that can open at program at run time.
and then there is there encryption certifications, that also has to updated.
Some programs will need to be recompiled from time to time, but not all programs require this.

Thanks for the help so far.


made no difference.

I did notice, though, that on my X5000 SSHTerm invokes repeated calls to OpenDevice(timer.device), whilst on the X1000 this does not happen. Not sure why there is a difference there, but that is the only one I see through use of SNOOPY.

I also ensured that all versions of all the libraries being opened by SSHTerm were the same on both machines, including the same version of AMISSL libs.

Interesting.

I now have a solution.

On the X5000 I can actually use the requester box and insert my password, but I must click on OK instead of pressing RETURN. If I press RETURN then I get an authentication failure. On the X1000 I can either press RETURN or click on OK.

Any ideas?

@rjd324

Is that perhaps the race condition?
When you press the ok button, the input string gadget looses focus, and it’s content is “registered”, but when you press enter, the enter is seen before the input string gadgets content has been registered.

Try tab first, and then enter? (Can’t remember if tab is standard way of moving out of gadgets so might not work.)

Solved with latest string.gadget.

Work around before that was to run Prefs->power at startup