add debug output to show which SSH key was selected for connection #249

New Issue

3wordchant · 2021-11-18T16:00:50Z

3wordchant commented

2021-11-18 16:00:50 +00:00

Describe the problem to be solved

There doesn't seem to be a way to see which SSH key abra chose for an SSH connection.

This can make it hard to debug key-selection issues with connections.

Describe the solution you would like

Add a DEBUG statement showing which SSH key was chosen.

## Describe the problem to be solved There doesn't seem to be a way to see which SSH key abra chose for an SSH connection. This can make it hard to debug key-selection issues with connections. ## Describe the solution you would like Add a DEBUG statement showing which SSH key was chosen.

3wordchant added the

enhancement

abra

labels 2021-11-18 16:00:50 +00:00

decentral1se referenced this issue from a commit

2021-11-18 19:05:23 +00:00

fix: log what keys are loaded with the ssh-agent

decentral1se closed this issue

2021-11-18 19:05:23 +00:00

decentral1se commented

2021-11-18 19:06:56 +00:00

Tested 56c3e070f5 and it seems to cover us here. We're lacking docs but abra supports building SSH connections with ssh-agent or using password auth so this commit asks the ssh-agent to list what keys it has loaded (which SSH will use one after the other until one matches afaiu).

Tested https://git.coopcloud.tech/coop-cloud/abra/commit/56c3e070f56e551c24f5a59153a418cdea1b5e65 and it seems to cover us here. We're lacking docs but `abra` supports building SSH connections with `ssh-agent` or using password auth so this commit asks the `ssh-agent` to list what keys it has loaded (which SSH will use one after the other until one matches afaiu).

decentral1se referenced this issue

2021-11-18 19:07:52 +00:00

Blocked on "ssh: handshake failed:" for server add flow #250

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#249