Update: The amazing folks at VanDyke have fixed SecureCRT so that if the session has a defined key, it is tried first; and if that key fails then agent keys are tried next.
The server has disconnected with an error. Server message reads:
A protocol error occurred. Too many authentication failures for ec2-user
Recently I was setting up EC2 instances for a client, and as such things go I wound up creating ssh keys for each of the EC2 regions in which I was working. With each instance I created in each new region, I configured the specific connection profile in SecureCRT with the appropriate ssh key. All was well, for a while. And then I hit a brick wall. I could spin up new instances, add them to SecureCRT, but I couldn’t connect to them.
Long story short, as I added each new ssh key, it was added to the “Agent Keys” that were automagically presented to each host. What I didn’t expect, and what I consider to be a bit of a bug, is that the Agent Keys are presented first; even if the session profile specifies a key. So, despite having configured a specific key for the session, my connections were failing because the X number of Agent Keys presented first exceeded MaxAuthTries in the sshd_config.
Many other ssh clients support Key Agent along with specified keys. OpenSSH and PuTTY are two that come to mind. OpenSSH will present Key Agent keys for auth, but if you specify “-i PATHtoKEYfile” that key will be presented first.
I reached out to support at VanDyke, the creators of SecureCRT. I explained the problem, and asked if there was a configuration option for controlling the Key Agent/Session Key order; and if not I requested that this be filed as a bug. I was told this “behavior is by design”. Odd, since they constructed a video explaining how Session settings override Default settings; so it is obvious they understand that most specific takes precedent over less specific settings. The same precedence should logically apply to auth keys, and it does with OpenSSH. According to section 188.8.131.52 “Using Identities” in SSH, The Secure Shell: The Definitive Guide the described behavior is host specific identities, and then agent identities.
The quickie solution I used was to got to “Tools”/”Manage Agent Keys” in SecureCRT and clear out all the extraneous keys that had accumulated. I hated doing this, as I was stripping out some of the ‘automatic smarts’ that I love about SecureCRT. Still, it isn’t as bad as the kludge that Todd at VanDyke support suggested. His suggestion was that I disable “Try All Agent Keys” in the SSH2.ini file. Todd’s suggestion makes me wonder why I pay money for SecureCRT and all of its advanced features if their only way to deal with a problem is to have me disable those features.
Despite several days of emailing back and forth, and providing documentation showing that at least two of the major ssh clients process host keys before agent keys, the folks at VanDyke stand by their odd choice of ordering. Todd has submitted a ‘feature request’ for me, and they refuse to treat this as a bug. Next time my license is up for renewal I just might have to write a SecureCRT->JellyfiSSH config conversion tool…