Ask Your Question

Revision history [back]

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-antispoof
option is required in plink.exe 0.73. It works latest 0.74.

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
option is required in plink.exe 0.73.

It works latest 0.74.

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

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

  1. https://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter7.html#plink-option-antispoof
  2. https://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter7.html#plink-usage-batch