Fix for "Brown Out" when trying to connect to Microsoft DevOps Repos #1090
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Microsoft introduced a "brownout" for SSH-RSA based authenticaction. In the future, only RSA-SHA2-256 and RSA-SHA2-512 are accepted. This does make a lot of sense, as the SHA-1 algorithm used for SSH-RSA authentication is not considered state of the art any more.
Details on SSH-RSA deprecaction:
https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/
This patch changes the configuration of the SSH client to use RSA-SHA2-256 and RSA-SHA2-512 only. It's not advised to keep using SSH-RSA.
The fix caused by go-git based program to work again.
I'm very sorry for not providing a unit-test and detailled bug reports with this fix. It does work - I'm using it in production. It's also very tiny, so you might be able to accept it from a simple review.
Otherwise, please feed back to me and I'll try to provide more material, as soon as I find the time.