KeeAgent support

[stevenengland]

Describe the problem: Hi everybody,

I found the issue issue here that is connected to what I want to achieve. But I can't see the solution to my problem there. I am using KeeAgent for KeePass (https://keeagent.readthedocs.io/en/stable/usage/quick-start.html). That one is able to act as a Pageant agent or client. Right now I want to use it as an agent. That works pretty well in other solutions like MobaXterm where I only need to set a config entry that MobaXterm shall use an "external Pageant". Then it finds my KeeAgent. But I cannot get tabby to use it. What has to be done to use an external Pageant?

To Reproduce:

• under tabby settings, go to SSH and choose an agent type (none worked for me)
• under tabby settings go to Profiles and connections and set the Authentication method to Agent

What happens:

 SSH  Connecting to 192.168.2.50
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  EQSye1GAIxn+b+wVDwrrXxxxxxxxxxxxxxxxxxxxxxxxxxx 
 X  All configured authentication methods failed
 SSH   X  Remote rejected opening a shell channel: Error: Not connected

Is there any related documentation for the topic of using an Pageant instance?

[Figoware]

Same problem for me with Alpha 183, using Pageant (tested on Pageant 0.74 and 0.76, just in case).

I reverted to Alpha 181 while waiting the fix!

[xtrafrancyz]

Same problem in Alpha 183. Version Alpha 181 is working fine.

Server OpenSSH_7.9p1 with pubkey auth only:

• Connection failed when agent auth is selected in profile
• Connection success when a private key is loaded into profile

Server OpenSSH_6.7p1 with pubkey auth only:

• Connection success with both agent or private key

My agent is Pageant via the KeeAgent plugin for KeePass.

[Hitman86R]

Same problem here

[sugibuchi]

The same problem here.

• KeeAgent + Tabby Alpha 181 -> OK
• KeeAgent + Tabby Alpha 182, 183 -> KO

[Vincent-HD]

Same here with windows OpenSSH agent, for now I pinned the version 181 with chocolatey 🤷‍♂️

[EDIT] By selecting the private key manually, tabby is able to connect, but when using the agent through Tabby it's not working. The agent is working properly inside a cmd

[stevenengland]

The same problem here.

* KeeAgent + Tabby Alpha 181 -> OK

* KeeAgent + Tabby Alpha 182, 183 -> KO

Hi @sugibuchi, I read your post and tried the same on my machine. I was not able to get it to work with 181. I am using KeeAgent 0.12.1.0 right now, other applications recognize that one pretty well. Can you help me out how to properly set up KeeAgent and Tabby 181?

[sugibuchi]

@stevenengland

Sorry for this delay. I use the following settings.

KeePass

• KeePass: 2.52
• KeeAgent: 0.13.2

KeePass -> Tools -> Options -> KeeAgent

• Agent Mode: Agent
• Uncheck all options
• Cygwin/MSYS integration
  • Check only "Create Cygwin compatible socket file" Path: C:\Users******\AppData\Local\Temp\cyglockfile

Windows environment variables

User variables

• SSH_AUTH_SOCK: C:\Users******\AppData\Local\Temp\cyglockfile

Tabby

• Binary: tabby-1.0.181-setup-x64.exe
• Profile:
  • Host, username etc.: as usual
  • Authentication method: Agent

[stevenengland]

Thanx a lot. I don't know why I never thought of having a look at some logs before... But when I finally did, I additionally found this: -> /var/log/auth.log Nov 2 21:02:37 graylog sshd[14940]: userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth] -> Google https://bbs.archlinux.org/viewtopic.php?pid=2041915#p2041915

So for hosts, where agent based logins still did not work the "trick" was to either use new ecdsa keys or modify sshd_conf because tabby somehow fails to use ssh-rsa.

[SOLVED] Latest sshd not accepting key algorithms / Networking, Server, and Protection / Arch Linux Forums

[sugibuchi]

Solved in my environment. I just downgraded the version of KeeAgent to 0.12.1 then it started working again with the latest Tabby (185) 🤔

[sugibuchi]

I have confirmed that the latest version of KeeAgant (0.13.3) works with Tabby 1.0.186.