Slackware 14.1, all up to date as per Slackware security mailing list.

Previously I used 2 programs on my Mac to access files on the Slackware machine, 1 uses sftp and the other scp.

Something I updated has made it so neither app can now connect, although I can still ssh into the box from a terminal on the same Mac without any problems.

Both the apps are up to date (and have had no updates since before the problem started), but I did update the Bash on the Mac because Apple didn't, but as I said ssh from a Bash prompt still works fine.

I am trying to nail down if the problem is from the Mac side or the Slack side, if it is Mac side I will ask for the thread to be closed and look for solutions in the correct section.

Here is what syslog says when the connections fail:

First, muCommander using sftp:
The above is when there is no Ciphers line in sshd_config, after googling I have tried adding a Ciphers line to sshd_config but it made no difference. The thing I think is odd is that the ciphers are all comma separated except for the bit that says 'server', is that normal from syslog? I have tried a Ciphers line with and without the server bit and with and without comma separating it but it makes no difference.

Second Komodo Edit using scp:
That's it! No amount of fiddling with password, username or port etc causes any other message, just that one as soon as the dialog box to enter the password to connect opens so it looks like it is failing before it really tries to start. Putting a file onto the Slack machine with scp from the terminal works fine

The only changes I can remember making to sshd_config were to set a different port, deny root login and permit login for only one specific username.

no matching cipher found:

client provides list "blowfish-cbc,3des-cbc"

server provides list "aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-
poly1305@openssh.com"

No overlap between lists -> FAIL.