 | 1 | initial version |
I have same issue, and solved by using plink.exe 0.70. But I dont't want to use vulnerable version of PuTTY ... I found plink.exe between 0.70 and 0.73 option changes affects default behavior. Finally, I identified
-no-antispoofoption is required in plink.exe 0.73. It works latest 0.74.
| | 2 | No.2 Revision |
I have same issue, and solved by using plink.exe 0.70. But I dont't want to use vulnerable version of PuTTY ... I found plink.exe between 0.70 and 0.73 option changes affects default behavior. Finally, I identified required that explicitly disable interactive input as follows:
-batch
or
-no-antispoof
see following link more detail
https://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter7.html#plink-option-antispoof https://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter7.html#plink-usage-batch
| | 3 | No.3 Revision |
I have same issue, and solved by using plink.exe 0.70. But I dont't want to use vulnerable version of PuTTY ... I found plink.exe between 0.70 and 0.73 option changes affects default behavior. Finally, I identified required that explicitly disable interactive input as follows:
-batch
or
-no-antispoof
It works latest 0.74.
see following link more detail
https://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter7.html#plink-option-antispoof
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
