Forum Discussion

Former Member's avatar
Former Member
4 years ago

Pageant Support and winssh-pageant

I'm really happy to be part of this beta program, currently have native \\.\pipe\openssh-ssh-agent windows supporting apps working. But this leaves quite a big gap in functionality on Windows.

I have been using winssh-pageant (https://github.com/ndbeals/winssh-pageant) as a translation layer between the Windows OpenSSH Agent and my Pageant supporting apps for 6 months with great success.

Now with 1password taking ownership of the ssh-agent pipe, if I access any application that uses the Pageant protocol the application freezes and the 1password.exe process goes to 100% single cpu core utilisation.

The 1p process stays at 100% until I quit and restart 1password.

Please advise if this setup is feasible and if there are any debugging details I can take to assist and if Pageant support is on the roadmap.

1Password Version: 8.6.0 (80600026 BETA)
Extension Version: 2.3.0 (BETA)
OS Version: Windows 11

SSH

12 Replies

Show More
  • floris_1P's avatar
    floris_1P
    Icon for 1Password Team rank1Password Team
    4 years ago

    Thanks for digging into this! We will investigate and get back to you.

  • Former Member's avatar
    Former Member
    4 years ago

    Some further details,

    Running the code for winssh-pageant directly (or running the compiled binary directly) works as expected. E.g. open PuTTY, ssh to host, enter username, 1password pops up.

    When running winssh-pageant via the authors recommended way (as a Scheduled Task set to run at Log On), it exhibits the behaviour I orginally posted. I suspect this may be connected to the owning process. This method has the ownership chain of winssh-pageant.exe -> svchost.exe (task scheduler) -> services.exe -> wininit.exe

    Running directly links back to the root explorer.exe process (under the same tree as 1password.exe is operating).

    Hope that helps. Outside of git usage, ssh key usage via PuTTY is my primary use case.