runconfig: temporary enable ssh client ssh-rsa sha1 signature algorithm #333
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.
Newer versions of openssh client disables ssh-rsa sha1 public key
signature algorithm.
Unfortunately gitea ssh server requires this signature algorithm instead
of using the stronger rsa-sha2-256/rsa-sha2-512 (see
go-gitea/gitea#17798)
So, as a temporary workaround, force enable on the ssh client the
ssh-rsa sha1 signature algorithm.
That's the reason why tests on run.agola.io are failing.
The new alpine/git image has a new openssh version disabling such algo.