mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-03-12 18:13:50 -05:00
9d687e4177
I tried setting this up on a different Windows machine today and had some slightly different experiences. I found that in at least some situations the command 'Include c:\...\pageant.conf' will cause OpenSSH to emit a log message saying it's trying to open the file '~/.ssh/c:\...\pageant.conf', which it then doesn't find. But 'Include pageant.conf' works, because that's interpreted relative to the .ssh directory that it's already found. (I don't know why this happened on one Windows machine and not another, since I only have a sample size of two. But an obvious guess would be a bug fix in the Windows OpenSSH port, present in the version on one of the machines I tried, and not in the other. Certainly that failure mode looks to me like 'apply Unix instead of Windows rules to decide what's an absolute pathname'.) Also, clarified that all of this only works with the version of OpenSSH that's available as a Windows optional feature, and not with the MSYS-based one that ships with Windows git.
This is the README for PuTTY, a free Windows and Unix Telnet and SSH
client.
PuTTY is built using CMake <https://cmake.org/>. To compile in the
simplest way (on any of Linux, Windows or Mac), run these commands in
the source directory:
cmake .
cmake --build .
Documentation (in various formats including Windows Help and Unix
`man' pages) is built from the Halibut (`.but') files in the `doc'
subdirectory using `doc/Makefile'. If you aren't using one of our
source snapshots, you'll need to do this yourself. Halibut can be
found at <https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is
https://www.chiark.greenend.org.uk/~sgtatham/putty/
If you want to send bug reports or feature requests, please read the
Feedback section of the web site before doing so. Sending one-line
reports saying `it doesn't work' will waste your time as much as
ours.
See the file LICENCE for the licence conditions.