feat: increase number of public key attempts before failing ssh

[rocketeerbkw]

General Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for inclusion in changelog

Problem

When using lagoon-cli to SSH or login, an error is returned: error: maximum authentication attempts exceeded.

Solution

Increase the MaxAuthTries of the SSH server. I arbitrarily multiplied the default by three.

18 keys ought to be enough for anybody.

Background

lagoon-cli will iterate over all of the keys in the system ssh-agent, but the order of the keys is non-deterministic. In the case where a user has more than six SSH keys, it's possible that the correct one is at the end of the list and the max auth attempts is exceeded.

Now that lagoon-cli and lagoon-sync have integrated SSH go libraries, they no longer call out to the system ssh binary. The side effect is that ssh client config files are no longer used. Previously, a user could set the IdentityFile in their ~/.ssh/config and avoid this problem.

The lagoon-cli can be configured with a specific ssh key (either in ~/.lagoon.yml or by passing -i) but then the user will be asked to enter their password for every command.

[shreddedbacon]

Can you make it configurable? That way if someone comes around later asking for 19, or 32 retries, they can adjust a chart value?

Edit: Use ep to envplate the sshd_config if it isn't already done, and use the same variable in the ssh-portal, chart can use global to configure both, or remote portals could then be configured independently

[smlx]

Rather than hacking around a client limitation in the server, can we add support for parsing the config file to lagoon-cli? e.g. I found https://github.com/kevinburke/ssh_config

edit: even simpler would be to add an identityfiles directive to lagoon-cli's config file with equivalent functionality to ssh_config's IdentityFile.

Some problems I see with the change in this PR:

• it will slow down SSH connections if you try 17 keys before finding the right one.
• people will still have trouble using multiple keys because there is no way to set the order. It is standard practice in SSH usage to have multiple keys. We should support that.
• eventually someone will come along with 19 keys in their agent and it will still break.

[shreddedbacon]

edit: even simpler would be to add an identityfiles directive to lagoon-cli's config file with equivalent functionality to ssh_config's IdentityFile.

This would be easy enough to do
Edit: already has the -i flag on lagoon-cli, but this bypasses the agent

[rocketeerbkw]

Rather than hacking around a client limitation in the server

IMHO it's the other way around, the server is limited and the previous "hack" was to set an IdentityFile directive for the lagoon ssh servers. Now we have to "hack" the lagoon-cli and lagoon-sync to also get around this limitation? We can just increase the number instead/in addition.

We've already had complaints from other users about this error, our response was "learn how to use SSH config." With that solution now gone (and let's be honest, now that I'm personally impacted), this very minor fix went to the top of my list.

edit: even simpler would be to add an identityfiles directive to lagoon-cli's config file with equivalent functionality to ssh_config's IdentityFile.

I addressed this in the OP. The cli has this option, but every command requires that you enter your password because it's no longer using the ssh-agent. It's the worst of all options.

can we add support for parsing the config file to lagoon-cli

Maybe? I looked at some solutions, there were a lot of questions about getting hostname globbing working correctly for example. While that's getting worked out, I can't SSH into environments until I reboot my computer enough times to get a order in ssh-agent that works.

it will slow down SSH connections

Source? I noticed no difference, maybe it delays by 10's of milliseconds? And it only slows down for users that have lots of keys.

This SO answer suggest that the expensive part is the initial connection, and each "auth try" is cheap.

It is standard practice in SSH usage to have multiple keys. We should support that.

This PR is to add support for more than 6 ssh keys, maybe I'm misunderstanding this comment?

@smlx would your concerns would be mitigated by a configurable MaxAuthTries that @shreddedbacon suggested, such that it can be set back to the default value at some point in the future if needed?

[smlx]

IMHO it's the other way around, the server is limited and the previous "hack" was to set an IdentityFile directive for the lagoon ssh servers. Now we have to "hack" the lagoon-cli and lagoon-sync to also get around this limitation? We can just increase the number instead/in addition.

MaxAuthTries 6 is the OpenSSH server default, so I don't think using IdentityFile in the client is really a hack. Also, increasing the number of tries doesn't address the use-case of multiple keys in the ssh-agent being used for different Lagoon accounts.

I addressed this in the OP. The cli has this option, but every command requires that you enter your password because it's no longer using the ssh-agent. It's the worst of all options.

What I meant is that in your ~/.lagoon.yml you could put something like:

lagoons:
    test:
        identityfiles:
        - ~/.ssh/id_ed25519_lagoon1.pub
        - ~/.ssh/id_ed25519_lagoon2.pub

And then, just like ssh does, lagoon-cli can prefer to use the keys from the identityfiles when using the agent. Would that work for your use-case?

[shreddedbacon]

What I meant is that in your ~/.lagoon.yml you could put something like:

lagoons:
    test:
        identityfiles:
        - ~/.ssh/id_ed25519_lagoon1.pub
        - ~/.ssh/id_ed25519_lagoon2.pub

And then, just like ssh does, lagoon-cli can prefer to use the keys from the identityfiles when using the agent. Would that work for your use-case?

How do tell the agent library in go to use a specific key in the agent? I couldn't find anything that described this clearly?

Edit: the CLI already has a flag to specify a key to use, but atm this is a forced bypass of the agent. So if the key is encrypted it will prompt a password. But if there is a way to pass this to the client to use when the agent is present, that would be a simple fix in the CLI.

Edit2: I think I see how it could work. Yep, I have a POC that can do this

[rocketeerbkw]

I'm all for also improving the cli experience, created an issue to discuss those details separately uselagoon/lagoon-cli#354.

[smlx]

Is this now addressed by uselagoon/lagoon-cli#355?