mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-10 09:58:01 +00: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. |
||
|---|---|---|
| .. | ||
| blurb.but | ||
| chm.css | ||
| chmextra.but | ||
| CMakeLists.txt | ||
| config.but | ||
| errors.but | ||
| faq.but | ||
| feedback.but | ||
| gs.but | ||
| index.but | ||
| intro.but | ||
| man-pageant.but | ||
| man-plink.but | ||
| man-pscp.but | ||
| man-psftp.but | ||
| man-psocks.but | ||
| man-psusan.but | ||
| man-pterm.but | ||
| man-putty.but | ||
| man-puttygen.but | ||
| man-puttytel.but | ||
| mancfg.but | ||
| manpages.but | ||
| pageant.but | ||
| pgpkeys.but | ||
| plink.but | ||
| pscp.but | ||
| psftp.but | ||
| pubkey.but | ||
| pubkeyfmt.but | ||
| site.but | ||
| sshnames.but | ||
| udp.but | ||
| using.but | ||
| vids.but | ||