-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no matching key exchange method found. #10642
Comments
_Ed25519_ does not yet seem to be supported, see microsoft/azure-pipelines-tasks#10642
Closed because this issue was mentioned in #11443. |
Ok, but does it work now? It seems not! |
Ok, thank you! Would be great, if this would work. |
FYI. #12317 contained solution to this one but I closed it now as it didn't got reviewed on ~1,5 years someone else of those who need this can try to create alternative PR. |
Ok, thank you! I will try to test it. |
Hi everyone! Current 'ssh2' version for CopyFilesOverSSHV0 task is 1.4.0, which should resolve this issue - please let us know if you still see it. |
I'm closing this due to inactivity, feel free to request a reopening if you have further questions. |
I am trying to copy my build Artifacts to my Linux Server using azure-piplines and this task:
The SSH Copy-Job always fails. My SSH log on the receiving end says:
I use
Ed25519
which is the most recommended public-key algorithm available today.any thoughts on when Azure-Pipeline-Tasks may support that? The offered key exchange methods seem a bit outdated AFAICT.
You can find the build here: https://dev.azure.com/ywesee/AmiKo_Csharp/_build/results?buildId=33
This may be related: #8818, https://github.com/MicrosoftDocs/vsts-docs/issues/3169
The text was updated successfully, but these errors were encountered: