You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using OpenSSH_8.9p1 Ubuntu-3ubuntu0.1, OpenSSL 3.0.2 15 Mar 2022
This version doesn't allow the usage of rsa keys (auth.log : userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth])
I can't provide an ED25519 key because it is clearly written in the specs it has to be a RSA key.
I tried allowing rsa temporarily to see if it works, unfortunately it didn't. Either way I wouldn't like to use something not secure enough. It would be better if there was a way to use ED25519 keys.
Is that possible somehow?
Thanks
The text was updated successfully, but these errors were encountered:
Having similar issues, not able to even do an FTP dry run. SSH version is not working either.
at Socket.<anonymous> (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/v4.3.4/dist/index.js:5288:33)
at Object.onceWrapper (node:events:641:28)
at Socket.emit (node:events:5[27](https://github.com/noxidsoft/workflow-test/actions/runs/5550196904/jobs/10135067628#step:3:28):[28](https://github.com/noxidsoft/workflow-test/actions/runs/5550196904/jobs/10135067628#step:3:29))
at Socket._onTimeout (node:net:516:8)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
Error: Error: Timeout (control socket)```
Hi,
I'm using OpenSSH_8.9p1 Ubuntu-3ubuntu0.1, OpenSSL 3.0.2 15 Mar 2022
This version doesn't allow the usage of rsa keys (auth.log : userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth])
I can't provide an ED25519 key because it is clearly written in the specs it has to be a RSA key.
I tried allowing rsa temporarily to see if it works, unfortunately it didn't. Either way I wouldn't like to use something not secure enough. It would be better if there was a way to use ED25519 keys.
Is that possible somehow?
Thanks
The text was updated successfully, but these errors were encountered: