Skip to content

Conversation

@hamza-db
Copy link

@hamza-db hamza-db commented Dec 4, 2025

Changes

I faced this issue myself when trying the expermental ssh tunnel. since I have couple of keys loaded into my ssh-agent

When a specific ssh key is provided via -i or IdentityFile option,the SSH client still attempt to auth using all keys loaded in the ssh-agent first. If too many keys are loaded, this causes the server to reject the connection with "Too many authentication failures" before the correct key is attempted.

Why

Tests

manually tested the change

When a specific ssh key is provided via `-i` or IdentityFile option,the SSH client may
still attempt to iterate through all keys loaded in the ssh-agent first.
If too many keys are loaded, this causes the server to reject the
connection with "Too many authentication failures" before the correct
key is attempted.
@github-actions
Copy link

github-actions bot commented Dec 4, 2025

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

  • PR number: 4095
  • Commit SHA: eecc3a236e49c71edc08369ea77b6d9d10b0bb78

Checks will be approved automatically on success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant