ui_pageant » Revisions »

Differences

This shows you the differences between the selected revisions of the page.

ui_pageant 2025-07-11		ui_pageant 2026-02-03 (current)
	Line 95:		Line 95:
	</code>		</code>

-	[[openssh]] Integrating with Windows OpenSSH ====	+	==== [[openssh]] Integrating with Windows OpenSSH ====

	Windows's own port of OpenSSH uses the same mechanism as Pageant to talk to its SSH agent (Windows named pipes). This means that Windows OpenSSH can talk directly to Pageant, if it knows where to find Pageant's named pipe.		Windows's own port of OpenSSH uses the same mechanism as Pageant to talk to its SSH agent (Windows named pipes). This means that Windows OpenSSH can talk directly to Pageant, if it knows where to find Pageant's named pipe.
	Line 113:		Line 113:
	Include pageant.conf		Include pageant.conf
	</code>		</code>
-	Note: this technique only works with Windows's port of OpenSSH, which lives at ''%SYSTEMROOT%\System32\OpenSSH\ssh.exe'' if you have it installed. (If not, it can be installed as a Windows optional feature, e.g., via //Settings > Apps & features > Optional features > Add a feature > OpenSSH Client//.) &wincp &winpath	+	Note: this technique only works with Windows's port of OpenSSH, which lives at ''%SYSTEMROOT%\System32\OpenSSH\ssh.exe'' if you have it installed. (If not, it can be installed as a Windows optional feature, via //Settings > System > Optional features//, on Windows 11 follow to //View features// and search "OpenSSH client", on Windows 10 click //Add a feature//.) &wincp &winpath &win11 &win10

	There are other versions of OpenSSH for Windows, notably the one that comes with Windows Git. Those will likely not work with the same configuration, because they tend to depend on Unix emulation layers like MinGW or MSys, so they won't speak Windows native pathname syntax or understand named pipes. The above instructions will only work with Windows's own version of OpenSSH.		There are other versions of OpenSSH for Windows, notably the one that comes with Windows Git. Those will likely not work with the same configuration, because they tend to depend on Unix emulation layers like MinGW or MSys, so they won't speak Windows native pathname syntax or understand named pipes. The above instructions will only work with Windows's own version of OpenSSH.