Regarding winscp backward compatibility!

Advertisement

gopikrishnakomanduri
Joined:
Posts:
7
Location:
India

Regarding winscp backward compatibility!

Hi,
I have used winscp382.exe for my project . My intention is to automate even security prompt for the user , when using winscp for the first time. I am copy pasting the script file , which I have used to transfer . Can I use the same script file for automation , even for later versions of winscp ? with my current script , can I say as I have generalized the winscp version , and can I say as user can choose any version of winscp and using my script , I can transfer like? Please let me know if I am not clear.

script I am using is,

option batch continue
option confirm on
open paraccel:paraccel@10.233.13.43
cd /home/paraccel
mkdir infa
cd infa
option transfer binary
put .\author2010-02-2218_19_38.228881.txt_1
close
exit


and launching winscp as
.\\winscp382.exe /script=.\\script.scr /log=.\\winscplog.txt"

Reply with quote

Advertisement

gopikrishnakomanduri
Joined:
Posts:
7
Location:
India

Re: Regarding winscp backward compatibility!

martin wrote:

You can use the same script with later versions of WinSCP.

Hi,
Thanks. But When I used the same script from winscp382.exe , it worked perfectly . But when tried with winscp4.2.6 (latest version) , it is not working . in winscp log file , I could see some logs like


. 2010-02-19 10:03:51.687 --------------------------------------------------------------------------
. 2010-02-19 10:03:51.687 WinSCP Version 4.2.6 (Build 721) (OS 5.2.3790 Service Pack 2)
. 2010-02-19 10:03:51.687 Login time: Friday, February 19, 2010 10:03:51 AM
. 2010-02-19 10:03:51.687 --------------------------------------------------------------------------
. 2010-02-19 10:03:51.687 Session name: paraccel@192.168.159.102
. 2010-02-19 10:03:51.687 Host name: 192.168.159.102 (Port: 22)
. 2010-02-19 10:03:51.687 User name: paraccel (Password: Yes, Key file: No)
. 2010-02-19 10:03:51.687 Tunnel: No
. 2010-02-19 10:03:51.687 Transfer Protocol: SFTP (SCP)
. 2010-02-19 10:03:51.687 Ping type: -, Ping interval: 30 sec; Timeout: 15 sec
. 2010-02-19 10:03:51.687 Proxy: none
. 2010-02-19 10:03:51.687 SSH protocol version: 2; Compression: No
. 2010-02-19 10:03:51.687 Bypass authentication: No
. 2010-02-19 10:03:51.687 Try agent: Yes; Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: No
. 2010-02-19 10:03:51.687 Ciphers: aes,blowfish,3des,WARN,arcfour,des; Ssh2DES: No
. 2010-02-19 10:03:51.687 SSH Bugs: -,-,-,-,-,-,-,-,-
. 2010-02-19 10:03:51.687 SFTP Bugs: -,-
. 2010-02-19 10:03:51.687 Return code variable: Autodetect; Lookup user groups: Yes
. 2010-02-19 10:03:51.687 Shell: default, EOL: 0
. 2010-02-19 10:03:51.687 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. 2010-02-19 10:03:51.687 LS: ls -la, Ign LS warn: Yes, Scp1 Comp: No
. 2010-02-19 10:03:51.687 Local directory: default, Remote directory: home, Update: No, Cache: Yes
. 2010-02-19 10:03:51.687 Cache directory changes: Yes, Permanent: Yes
. 2010-02-19 10:03:51.687 DST mode: 1
. 2010-02-19 10:03:51.687 --------------------------------------------------------------------------
. 2010-02-19 10:03:51.687 Looking up host "192.168.159.102"
. 2010-02-19 10:03:51.687 Connecting to 192.168.159.102 port 22
. 2010-02-19 10:03:51.718 Server version: SSH-1.99-OpenSSH_3.9p1
. 2010-02-19 10:03:51.718 Using SSH protocol version 2
. 2010-02-19 10:03:51.718 We claim version: SSH-2.0-WinSCP_release_4.2.6
. 2010-02-19 10:03:51.734 Doing Diffie-Hellman group exchange
. 2010-02-19 10:03:51.796 Doing Diffie-Hellman key exchange with hash SHA-1
. 2010-02-19 10:03:51.937 Asking user:
. 2010-02-19 10:03:51.937 The server's host key was not found in the cache. You have no guarantee that the server is the computer you think it is.
. 2010-02-19 10:03:51.937
. 2010-02-19 10:03:51.937 The server's rsa2 key fingerprint is:
. 2010-02-19 10:03:51.937 ssh-rsa 1024 6d:f6:59:c7:42:e4:3d:51:00:56:13:48:40:c9:66:e8
. 2010-02-19 10:03:51.937
. 2010-02-19 10:03:51.937 If you trust this host, press Yes. To connect without adding host key to the cache, press No. To abandon the connection press Cancel.
. 2010-02-19 10:03:51.937
. 2010-02-19 10:03:51.937 Continue connecting and add host key to the cache? ()
. 2010-02-19 10:03:51.937 Attempt to close connection due to fatal exception:
* 2010-02-19 10:03:51.937 Host key wasn't verified!
. 2010-02-19 10:03:51.937 Closing connection.
. 2010-02-19 10:03:51.937 Sending special code: 12

May I know is this the bug in winscp4.2.6 or am I doing any thing wrong? Please correct me if I am wromg .

Thx,
--Gopi

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
40,476
Location:
Prague, Czechia

Re: Regarding winscp backward compatibility!

gopikrishnakomanduri wrote:

May I know is this the bug in winscp4.2.6 or am I doing any thing wrong? Please correct me if I am wromg .
I suppose you are running 4.2.6 on different machine than the old version. Or you run it under different user or with different configuration (INI file).

Please read documentation. If that does not help, come back.

Reply with quote

Advertisement

You can post new topics in this forum