tag:blogger.com,1999:blog-4901161376749146054.post1903580313952167467..comments2024-03-03T21:42:48.778-08:00Comments on WinSSHTerm: new version 2.23.1 releasedPSthttp://www.blogger.com/profile/07212427948074030359noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4901161376749146054.post-23929218190290596382022-08-24T13:36:05.128-07:002022-08-24T13:36:05.128-07:00Thanks, this should be fixed in version 2.23.2Thanks, this should be fixed in version 2.23.2PSthttps://www.blogger.com/profile/07212427948074030359noreply@blogger.comtag:blogger.com,1999:blog-4901161376749146054.post-9964837934156533022022-08-22T10:25:34.134-07:002022-08-22T10:25:34.134-07:00Amazing work as always. I was curious if this new...Amazing work as always. I was curious if this new plink -pwfile function worked with token auth? I'm getting an error when trying to use plink now with my jump server, whereas the previous version (months ago) was working.<br /><br />=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2022.08.22 11:20:14 =~=~=~=~=~=~=~=~=~=~=~=<br />Event Log: Leaving host lookup to proxy of "10.247.XXX.XX" (for SSH connection)<br />Event Log: Starting local proxy command: plink -P 22 -l myaccountname server.test.com -nc 10.247.XXX.XX:22 -pwfile \"\\\\.\\PIPE\\ffb17154-5c3b-4c5a-94d6-9f9a53abb380\"<br />Event Log: We claim version: SSH-2.0-PuTTY_Release_0.77<br />Event Log: Connected to 10.247.XXX.XX<br />Event Log: proxy: plink: unable to read a password from file '\\.\PIPE\ffb17154-5c3b-4c5a-94d6-9f9a53abb380'<br />Event Log: Remote side unexpectedly closed network connection<br />Peterhttps://www.blogger.com/profile/16250775248037812303noreply@blogger.com