[英]What endpoint does the Windows OpenSSH Agent listen on
Does anybody know what endpoint the Windows OpenSSH Authentication agent listens on, and how it advertises this so that the Windows ssh.exe
can communicate with it?有谁知道 Windows OpenSSH 身份验证代理侦听的端点是什么,以及它如何宣传它以便 Windows
ssh.exe
可以与之通信?
I know I'm a bit late to the party, but I recently noticed that my Windows PC has a service called "OpenSSH Authentication Agent", which is disabled by default.我知道我来晚了一点,但我最近注意到我的 Windows PC 有一项名为“OpenSSH 身份验证代理”的服务,默认情况下是禁用的。 When enabled, it works quite well as the ssh-agent for the
ssh.exe
that comes with Windows 10 and later ( C:\Windows\System32\OpenSSH
).启用后,它与
ssh.exe
的 ssh 代理一样工作得很好,它随 Windows 10 及更高版本 ( C:\Windows\System32\OpenSSH
) 一起提供。
In Unix operating systems the ssh-agent
listens on a Unix socket, and the location of that socket is set in the SSH_AUTHSOCK
environment variable.在 Unix 操作系统中,
ssh-agent
侦听 Unix 套接字,并且该套接字的位置在SSH_AUTHSOCK
环境变量中设置。 However in Windows there is no SSH_AUTH_SOCK
environment variable and the Windows-supplied ssh.exe
seems to find it anyway.但是在 Windows 中没有
SSH_AUTH_SOCK
环境变量,Windows 提供的ssh.exe
似乎无论如何都能找到它。
Furthermore, It's my understanding that Windows does not implement Unix sockets, so ssh.exe
must be using a different mechanism.此外,据我了解,Windows 没有实现 Unix sockets,因此
ssh.exe
必须使用不同的机制。
It's open source that is hosted on Github here它是开源的,托管在Github here
The wrapper tha runs ssh-agent as a Windows service is in the source tree here运行 ssh-agent 作为 Windows 服务的包装器位于此处的源代码树中
And a quick glance of the code ( agent.c ) suggests that a Win32 named pipe is the IPC mechanism.快速浏览一下代码 ( agent.c ) 表明名为 pipe 的 Win32 是 IPC 机制。 You might want to dive deeper into the code including building, running and debugging locally.
您可能想要更深入地研究代码,包括在本地构建、运行和调试。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.