Forum » Support and Bug Reports »

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.

Username

Subject

Message body

Font colour:

Font size:

Options

Disable BBCode in this post

Notify me when a reply is posted (registered users only)

Add an Attachment

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

Filename

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

File Comment

Options

Private file (available to author and site moderators only)

Topic review

Itsuka

Re: Regarding the sequence violation when using scripts in winsc

2013-12-12 07:17

I feel that Winscp is a great software. :D
However, it does not work well with our server. Therefore, we are considering using other client softwares.
Thank you for your reply.

martin

Re: Regarding the sequence violation when using scripts in winsc

2013-12-11

According to the vendor’s reply, if the product has been created based on RFC4254 ,draft-ietf-secsh-filexfer-02 and etc, it seems that the SSH_FXP_CLOSE message should return a reply.

Indeed. But I do not see any requirement that a client needs to wait for it. No other server ever had a problem with this.

Is winscp going to remain as its current state of not waiting for a reply, without an update in the future?

Unless I get convinced that it is a bug.

Guest

Re: Regarding the sequence violation when using scripts in winsc

2013-12-10 11:47

Thank you for your reply.

According to the vendor’s reply, if the product has been created based on RFC4254 ,draft-ietf-secsh-filexfer-02 and etc, it seems that the SSH_FXP_CLOSE message should return a reply.

Which standard does winscp base on to determine whether to wait or not for a reply from the message, or whether to sync or not using a script command?

Is winscp going to remain as its current state of not waiting for a reply, without an update in the future?

martin

Re: Regarding the sequence violation when using scripts in winsc

2013-12-06

Ok, I see the point now. It's true that WinSCP does not wait for confirmation of "file close" request. But I'm not ware of any obligation to do that. So I do not think this "violation" of anything.

Itsuka

Re: Regarding the sequence violation when using scripts in winsc

2013-12-06 09:13

Thank you for your reply.

Please allow me to send the log to you.
I generated it using winscp5.1.7.
The log's output destination and the script name is different from those in the enquiry I posted above.
However, the problem still remains the same.

script　details
open XXXXXXXX@XXXXXXX
lcd d:\

get /edidata/TST00003S/TST003SS
close
exit

martin

Re: Regarding the sequence violation when using scripts in winsc

2013-12-04

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, use /log=path_to_log_file command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.

Itsuka

Regarding the sequence violation when using scripts in winsc

2013-12-03 11:47

When connecting to the SFTP server in winscp, (Using scripts) because the SFTP server will output an error and then terminate. :cry:

According to the vendor who provided the SFTP server, when scripts of winscp are used,
errors will occur in the SFTP server because the data transmission in the winscp will violate the sequence.

After winscp sent the files using the ‘get’ command, the ‘close’ request was submitted.
Without waiting for the reply from the server, the transport channel terminated.
Due to that reason, errors occurred in the server because the client did not receive a normal termination of the file closing.
Is this a bug of winscp in which the close request was submitted and the reply was not received . Is there a way to avoid this problem?

The following are the scripts and commands.

"C:\Program Files\WinSCP\WinSCP.com" /script=d:\sftp_test\test.scp /log=d:\sftp_test\test.log

test.scp ‘s details
open XXXXX@XXXXXX
get XXXXXX.txt
close
exit