Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

open \\.\pipe.openssh-ssh-agant:Access is denied #82

Open
2944721178 opened this issue Apr 7, 2023 · 7 comments
Open

open \\.\pipe.openssh-ssh-agant:Access is denied #82

2944721178 opened this issue Apr 7, 2023 · 7 comments

Comments

@2944721178
Copy link

image
我一直在报这个错误
image
该服务也处于禁用状态
点击github下载的WinSryptSSHAgent,任务管理器会有该进程,但会出现那个报错,结束进程后重新启动仍然无效

@fredzhu
Copy link

fredzhu commented May 27, 2023

same issue

@airtonix
Copy link

airtonix commented Aug 29, 2023

getting same error.

image

image

@simonkimi
Copy link

simonkimi commented Aug 29, 2023

检查一下是不是有其他agent也在运行, 我才发现1password也有ssh-agent, 会导致这个用不了

Check if there are other agents running, I just found out that 1password also has ssh-agent, which causes this one to not work.

@airtonix
Copy link

airtonix commented Sep 1, 2023

Check if there are other agents running, I just found out that 1password also has ssh-agent, which causes this one to not work.

@simonkimi how did you do this?

@simonkimi
Copy link

Check if there are other agents running, I just found out that 1password also has ssh-agent, which causes this one to not work.

@simonkimi how did you do this?

@airtonix

  1. Download Process Explorer

  2. Toolbar > Find > Find Handle or DLL or press ctrl + shift + F
    图片

  3. Search \Device\NamedPipe\ and wait for a while, You will find which process is occupied openssh-ssh-agant
    图片

@airtonix
Copy link

airtonix commented Sep 4, 2023

Ok I get a bunch of results, but none of them list \Device\NamedPipe\openssh-ssh-agent

edit:

ok i had to run process explorer as administrator.

turns out my instance of \Device\NamedPipe\openssh-ssh-agent was the one in my screenshot above ☝🏻 😅

so killing that and restarting wincrypt i no longer get the startup error.

but i still cant get this working in wsl :<

@MaKraMc
Copy link

MaKraMc commented Jan 16, 2024

This error also seems to occur when multiple users are trying to run WinCryptSSHAgent.
eg. User 1 logs in and runs the program. User 2 logs in later and runs the program while it is still running on user1's account on the same machine. The Program still works but the error message gets displayed.
Should I open a separate issue for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants