Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

terry09

Re: Upload of text fileIn PuTTY 0.68 through 0.80 before 0.81, biased ECDSA noncs using command line

In PuTTY 0.68 through 0.80 before 0.81, biased ECDSA nonce generation allows an attacker to recover a user's NIST P-521 secret key via a quick attack in approximately 60 signatures. This is especially important in a scenario where an adversary is able to read messages signed by PuTTY or Pageant. The required set of signed messages may be publicly readable because they are stored in a public Git service that supports use of SSH for commit signing, and the signatures were made by Pageant through an agent-forwarding mechanism. In other words, an adversary may already have enough signature information to compromise a victim's private key, even if there is no further use of vulnerable PuTTY versions. After a key compromise, an adversary may be able to conduct supply-chain attacks on software maintained in Git. A second, independent scenario is that the adversary is an operator of an SSH server to which the victim authenticates (for remote login or file copy), even though this server is not fully trusted by the victim, and the victim uses the same private key for SSH connections to other services operated by other entities. Here, the rogue server operator (who would otherwise have no way to determine the victim's private key) can derive the victim's private key, and then use it for unauthorized access to those other services. If the other services include Git services, then again it may be possible to conduct supply-chain attacks on software maintained in Git. This also affects, for example, FileZilla before 3.67.0, WinSCP before 6.3.3, TortoiseGit before 2.15.0.1, and TortoiseSVN through 1.14.6.
martin

Re: using port number in scripting

arwind wrote:

I was using scripting file to automation copy file from PC A to PC B. It's running well, but when PC A using PORT that scripting not running.

Do you mean that it does not work, when you need to specify port number in script? What protocol is the server using?
arwind

using port number in scripting

Hi,
I was using scripting file to automation copy file from PC A to PC B. It's running well, but when PC A using PORT that scripting not running.

That script :
option batch on
option confirm off
open abcd:abcdefg@202.66.66.1:5550
cd /usr/local/
option transfer binary
lcd c:\
get *
close
exit

please help me! :-(
arwind
martin

Re: Upload of text files using command line

Please read documentation.
Guest

Re: Upload of text files using command line

Me wrote:

Hi,

I setup WINSCP to transfer a txt file to a sftp server. The file is transferred but the format changes. Are there any option to specify transfer mode and file system (win/unix) in command mode? I can't find any info about it.


I use the sample file for scripting and start it from SQL server on a Windows server. FTP server is using Globalscape SFTP server and I believe it is a Windows server, though I'm not sure.


I use

option batch on
option confirm off
open xxx:yyy@zz.zz.zz.zz
put e:\data\1.txt
close
exit

Need to know how I can force BIn instead of ascii, which is used by default. That was the problem.
Me

Upload of text files using command line

Hi,

I setup WINSCP to transfer a txt file to a sftp server. The file is transferred but the format changes. Are there any option to specify transfer mode and file system (win/unix) in command mode? I can't find any info about it.


I use the sample file for scripting and start it from SQL server on a Windows server. FTP server is using Globalscape SFTP server and I believe it is a Windows server, though I'm not sure.