We have moved to a new Sailfish OS Forum. Please start new discussions there.
3

ssh stopped working [answered]

asked 2019-06-25 01:33:31 +0200

omichalek gravatar image

Hi all,

Ever since I think the last but one update ago I can no longer ssh into SFOS, it gives this error:

ssh_dispatch_run_fatal: Connection to 10.0.0.123 port 22: message authentication code incorrect

Running Xperia X, I use keys (no password). How can I fix it please?

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Maus
close date 2019-06-27 12:54:53.274852

Comments

What happens if you try the user@server password way? Does this work?

dirksche ( 2019-06-25 08:26:36 +0200 )edit
1

hm, same here after updating my old jolal c from 3.0.2.8 to 3.0.3.10

coderus ( 2019-06-25 16:47:17 +0200 )edit

happened to me after upgrade to Seitseminen .. had to "ssh -c aes128-ctr -m hmac-sha1 " and apply sshd_config.rpmnew to sshd_config .

shanti ( 2019-07-30 14:49:10 +0200 )edit

1 Answer

Sort by » oldest newest most voted
8

answered 2019-06-25 14:23:54 +0200

jayki gravatar image

updated 2019-06-25 14:25:19 +0200

Please check /etc/ssh/sshd_config

There are some broken ciphers which have to be disabled. Jollas ssh packages should disable them but if you have installed any other openssh package they won't.

In fact you need to add this line (which normally should already be there):

Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com

(It's listed like this in original sshd_config: ) Cipher chacha20-poly1305@openssh.com causes connection error with openssh compiled with gcc 4.9.4: "message authentication code incorrect". This is probably a compiler/openssh bug but as a workaround drop the chacha cipher from supported list for now (see JB#44920).

edit flag offensive delete publish link more

Comments

Thanks, it solved the issue on Sailfish OS version 3.0.3.10. The file /etc/ssh/sshd_config did not have this line (only /etc/ssh/sshd_config.rpmnew had it). The issue happened after a firmware update even if I never installed any other OpenSSH package. By the way, what do you mean by JB#44920?

baptx ( 2019-07-10 11:36:44 +0200 )edit

Question tools

Follow
6 followers

Stats

Asked: 2019-06-25 01:33:31 +0200

Seen: 846 times

Last updated: Jun 25 '19