Conference annecy::ftso

Hi,

First, FTSO version 1.2 accept password string with 24 characters max. 

Second, could you check that you are able to transfer the file with FTP instead FTSO.

If it is possible throught FTP, could you try it with FTSO in BASIC FTPMODE. In case it is not
success, follow these instructions : 

The error FTP__REMERROR is returned by the FTP server on the remote machine, and is not
recognize by the FTSO client parts on your local machine. FTSO uses a FTP library  on the
client parts. We have detected a problem with this library. 

Copy the new library. You can find a new library on
	- AEOENG::FTSO$PUBLIC:CALLFTPVAX013.A;1 for OpenVMS VAX 5.5-2 or higher
	- AEOENG::FTSO$PUBLIC:CALLFTPAXP013.A;1 for OpenVMS AXP 6.1 or higher

Stop FTSO with SYS$STARTUP:FTSO_SHUTDOWN.COM

Install the library with vmsinstal.

Restart with SYS$STARTUP:FTSO_STARTUP.COM

Hope this can help
Emmanuel.

Hello,

I'm trying to use FTSO to transfer data between and VMS V6.1 and NT 
V4.0 server. I have FTSO V1.3-1 installed on both platforms and I have 
the two problem.

Problem 1

If I use FTSO I can transfer one file from the VMS to the NT server ok. 
The problem arises when I try to transfer multiple files. If I use FTSO 
in Normal mode then the *.biq files get created on the NT server but the 
job fails with 

FTSO Job: 0013  (F)  Posted at: Thu Apr 10 15:07:58 1997  By: SYSTEM
Command: copy *.* thesrc/user/ftsouser::*.*
Completed at: Thu Apr 10 15:09:46 1997  Status: error
Transfer: LAT$SYSTARTUP.COM 
thesrc/user/**********::*.*LAT$SYSTARTUP.COM
Terminated at: Thu Apr 10 15:08:26 1997  Status: error
%FTSO-E-PROTOCOL, error return code in protocol message, Msg_type 
35, Reason 001
%FTSO-E-TASKFAIL, secondary job 001301 has failed

and the files never get converted.

If I use FTP then the files get copied over correctly with no problems.

If I try to use FTSO in FTPMODE BASIC then nothing gets copied over 
to the NT server and the job fails with 

FTSO Job: 0016  (F)  Posted at: Thu Apr 10 16:00:51 1997  By: SYSTEM
Command: copy *.* thesrc/user/ftsouser::*.* ftpmode basic
Completed at: Thu Apr 10 16:01:55 1997  Status: error
Transfer: LAT$SYSTARTUP.COM 
thesrc/user/**********::*.*LAT$SYSTARTUP.COM
Terminated at: Thu Apr 10 16:01:09 1997  Status: error
%cftp_put_file, FTP__REMERROR - 550 *.*LAT$SYSTARTUP.COM: 
The filename, director
y name, or volume label syntax is incorrect.
%FTSO-E-TASKFAIL, secondary job 001601 has failed

I have copied over the CFTP library file and installed them but they 
provide no additional details.

Problem 2

The other area is the passing of the password. If I run a network 
analyser to look at the data that gets passed when I transfer one file 
using FTSO then I can see the password. I thought I had read that 
FTSO didn't pass the password as clear text.

Any help would be great.

Thanks,

Gary

Hi,

Does any one have any thoughts on my problems described in the 
previous note?.

Thanks,

Gary

Hi, 

Concerning your problem number 1, you can use wildcards to specify several source files, but you should not use
them for the destination files. I mean you must use the following syntax :

		ftso copy *.* host/user/password::

and NOT		ftso copy *.* host/user/password::*.*

(see examples in the ftso user guide).

Try this, if there are no other problems, it should be working.

Concerning the problem number 2, it seems very strange. We are working on it...

Thanks

Christophe THIVEL

Here is the answer to the problem of uncrypted password :

In any case, the FTSO protocol doesn't transfer the password to the remote machine. So, if you can see this
password using a network analyser, it must be on the FTP port number 21, because the FTP protocol is the only
responsible of the identification of remote user and password.

So if the password appears in clear, it is only due to the FTP protocol which probably doesn't encrypt the
password.

Christophe THIVEL

Thanks for the pointers. The syntax error on the copy command sorted 
out the 550 errors.

If your information is right then it looks as though the FTSO job on the 
VMS system is failing to connect correctly to the FTSO service on the 
NT server and is then falling back to using FTP. The FTSOxxx.LOG file 
just says that the job completed. Is there any more information I can get 
to find out why the FSTO connection isn't made.

Thanks,

Gary

Hi,

If you have problems to make a connection, you can get more information on the
job by setting a logical called FTSO_DEBUG :
	define FTSO_DEBUG "ON"

This will generate a debug log file in the ftso directory :
	SYS$SYSDEVICE:[FTSO]FTSO_DEBUG_XXXX.LOG
where XXXX is the job number.

Could you make another test and explain us exactly what you do and what you get
in this debug file.
Thanks

Christophe

Hi,

From the VMS system I am executing the following command:

FTSO> copy *.*   'NT server'/'username'/'password'::

The batch job gets created, the job runs and the files are copied to the NT server.

The debug contains the following:

Tue Apr 22 07:23:56 1997 <0033> FTSO_CLTP_MAIN\main - started
Tue Apr 22 07:23:57 1997 <0033> FTSO_CLTP_SCHEDULER\ftso_submit_tasks - 
secondary task submitted
Tue Apr 22 07:23:58 1997 <0033> FTSO_CLTP_SCHEDULER\ftso_submit_tasks - 
secondary task submitted
Tue Apr 22 07:23:59 1997 <0033> FTSO_CLTP_SCHEDULER\ftso_submit_tasks - 
secondary task submitted
Tue Apr 22 07:24:01 1997 <0033> FTSO_CLTP_SCHEDULER\ftso_submit_tasks - 
secondary task submitted
Tue Apr 22 07:24:01 1997 <0033> FTSO_CLTP_MAIN\main - successfully 
submitted tasks
Tue Apr 22 07:24:06 1997 <003301> FTSO_CLTS_MAIN\ftso_initialize - started
Tue Apr 22 07:24:07 1997 <003301>  -- privilege current mask : ffffffff ffffffff
Tue Apr 22 07:24:09 1997 <003301>  -- privilege mask input   : ffffffff ffffffff
Tue Apr 22 07:24:09 1997 <003302> FTSO_CLTS_MAIN\ftso_initialize - started
Tue Apr 22 07:24:10 1997 <003301>  -- privilege mask set to  : ffffffff ffffffff
Tue Apr 22 07:24:11 1997 <003302>  -- privilege current mask : ffffffff ffffffff
Tue Apr 22 07:24:11 1997 <003301> FTSO_CLTS_SCHEDULER\ftso_remote_copy - 
remote file copy started
Tue Apr 22 07:24:12 1997 <003302>  -- privilege mask input   : ffffffff ffffffff
Tue Apr 22 07:24:12 1997 <003301> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - started
Tue Apr 22 07:24:12 1997 <003301> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - started
Tue Apr 22 07:24:12 1997 <003302>  -- privilege mask set to  : ffffffff ffffffff
Tue Apr 22 07:24:13 1997 <003303> FTSO_CLTS_MAIN\ftso_initialize - started
Tue Apr 22 07:24:13 1997 <003301> FTSO_CLTS_PROTOCOL_MANAGER\remote 
host connection
Tue Apr 22 07:24:14 1997 <003302> FTSO_CLTS_SCHEDULER\ftso_remote_copy - 
remote file copy started
Tue Apr 22 07:24:15 1997 <003304> FTSO_CLTS_MAIN\ftso_initialize - started
Tue Apr 22 07:24:15 1997 <003303>  -- privilege current mask : ffffffff ffffffff
Tue Apr 22 07:24:16 1997 <003302> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - started
Tue Apr 22 07:24:16 1997 <003303>  -- privilege mask input   : ffffffff ffffffff
Tue Apr 22 07:24:17 1997 <003304>  -- privilege current mask : ffffffff ffffffff
Tue Apr 22 07:24:17 1997 <003302> FTSO_CLTS_PROTOCOL_MANAGER\remote 
host connection
Tue Apr 22 07:24:18 1997 <003303>  -- privilege mask set to  : ffffffff ffffffff
Tue Apr 22 07:24:18 1997 <003304>  -- privilege mask input   : ffffffff ffffffff
Tue Apr 22 07:24:19 1997 <003303> FTSO_CLTS_SCHEDULER\ftso_remote_copy - 
remote file copy started
Tue Apr 22 07:24:19 1997 <003301> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_build_initialize_c
Tue Apr 22 07:24:20 1997 <003304>  -- privilege mask set to  : ffffffff ffffffff
Tue Apr 22 07:24:20 1997 <003303> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - started
Tue Apr 22 07:24:20 1997 <003301> FILE ATTRIBUTES : ORG=0 RFM=4 RAT=2 
MRS=0 mode=0
Tue Apr 22 07:24:21 1997 <003304> FTSO_CLTS_SCHEDULER\ftso_remote_copy - 
remote file copy started
Tue Apr 22 07:24:21 1997 <003303> FTSO_CLTS_PROTOCOL_MANAGER\remote 
host connection
Tue Apr 22 07:24:22 1997 <003304> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - started
Tue Apr 22 07:24:22 1997 <003302> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_build_initialize_c
Tue Apr 22 07:24:23 1997 <003304> FTSO_CLTS_PROTOCOL_MANAGER\remote 
host connection
Tue Apr 22 07:24:24 1997 <003301> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - logged in 
successfully
Tue Apr 22 07:24:24 1997 <003302> FILE ATTRIBUTES : ORG=0 RFM=4 RAT=2 
MRS=0 mode=0
Tue Apr 22 07:24:25 1997 <003301> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_file_transfer_send - started
Tue Apr 22 07:24:26 1997 <003303> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_build_initialize_c send - started
Tue Apr 22 07:24:26 1997 <003303> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_build_initialize_c
Tue Apr 22 07:24:27 1997 <003303> FILE ATTRIBUTES : ORG=0 RFM=2 RAT=2 
MRS=255 mode=0
Tue Apr 22 07:24:27 1997 <003302> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - logged in 
successfully
Tue Apr 22 07:24:28 1997 <003304> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_build_initialize_c
Tue Apr 22 07:24:28 1997 <003302> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_file_transfer_send - started
Tue Apr 22 07:24:29 1997 <003301> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_terminate_transfer - started
Tue Apr 22 07:24:29 1997 <003304> FILE ATTRIBUTES : ORG=0 RFM=2 RAT=8 
MRS=512 mode=0
Tue Apr 22 07:24:30 1997 <003303> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - logged in 
successfully
Tue Apr 22 07:24:30 1997 <003301> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_terminate_transfer - finished
Tue Apr 22 07:24:31 1997 <003302> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_terminate_transfer - started
Tue Apr 22 07:24:31 1997 <003303> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_file_transfer_send - started
Tue Apr 22 07:24:31 1997 <003301> 
FTSO_CLTS_SCHEDULER\ftso_job_completion - job completion started
Tue Apr 22 07:24:31 1997 <003303> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_file_transfer_send - started
Tue Apr 22 07:24:31 1997 <003301> 
FTSO_CLTS_SCHEDULER\ftso_job_completion - job completion started
Tue Apr 22 07:24:32 1997 <003304> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_initialize_transfer - logged in 
successfully
Tue Apr 22 07:24:33 1997 <003302> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_terminate_transfer - finished
Tue Apr 22 07:24:33 1997 <003301> 
FTSO_CLTS_SCHEDULER\ftso_job_completion - job completion finished
Tue Apr 22 07:24:33 1997 <003304> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_file_transfer_send - started
Tue Apr 22 07:24:34 1997 <003303> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_terminate_transfer - started
Tue Apr 22 07:24:34 1997 <003302> 
FTSO_CLTS_SCHEDULER\ftso_job_completion - job completion started
Tue Apr 22 07:24:35 1997 <003301> %FTSO-I-TASKCOMPLETED, Secondary job 
003301 has successfully completed
Tue Apr 22 07:24:35 1997 <003303> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_terminate_transfer - finished
Tue Apr 22 07:24:35 1997 <003304> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_terminate_transfer - started
Tue Apr 22 07:24:36 1997 <003302> 
FTSO_CLTS_SCHEDULER\ftso_job_completion - job completion finished
Tue Apr 22 07:24:36 1997 <003301> %cftp_close, invalid FTP descriptor
ue Apr 22 07:24:37 1997 <003303> FTSO_CLTS_SCHEDULER\ftso_job_completion 
- job completion started
Tue Apr 22 07:24:37 1997 <003302> %FTSO-I-TASKCOMPLETED, Secondary job 
003302 has successfully completed
Tue Apr 22 07:24:38 1997 <003304> 
FTSO_CLTS_PROTOCOL_MANAGER\ftso_terminate_transfer - finished
Tue Apr 22 07:24:39 1997 <003303> 
FTSO_CLTS_SCHEDULER\ftso_job_completion - job completion finished
Tue Apr 22 07:24:39 1997 <003302> %cftp_close, invalid FTP descriptor
Tue Apr 22 07:24:40 1997 <003304> 
FTSO_CLTS_SCHEDULER\ftso_job_completion - job completion started
Tue Apr 22 07:24:40 1997 <003303> %FTSO-I-TASKCOMPLETED, Secondary job 
003303 has successfully completed
Tue Apr 22 07:24:41 1997 <003304> 
FTSO_CLTS_SCHEDULER\ftso_job_completion - job completion finished
Tue Apr 22 07:24:41 1997 <003303> %cftp_close, invalid FTP descriptor
Tue Apr 22 07:24:42 1997 <003304> %FTSO-I-TASKCOMPLETED, Secondary job 
003304 has successfully completed
Tue Apr 22 07:24:42 1997 <003304> %cftp_close, invalid FTP descriptor
Tue Apr 22 07:24:44 1997 <0033> FTSO_CLTP_SCHEDULER\ftso_job_completion - 
job completion started
Tue Apr 22 07:24:48 1997 <0033> FTSO_CLTP_SCHEDULER\ftso_job_completion - 
job completion finished

In the debug file the only error I can see are the 'invalid FTP descriptor'.

When I look at the network trace I can see the VMS system making requests to port 
0x07CB (1995) on the NT server. There is an exchange of a few packets between 
these ports, then I see the NT  server send an FTP logon banner ' 220 xxxx Microsoft 
FTP Version 2.0). The VMS system responds with the User name and then the 
password. A files is then transferred and the FTP session is closed. The FTP session 
is then opened again and the next file is sent.

The FTSO service is running on the NT server under the System account.

Thanks,

Gary
   

Hi,

When we have a look to your debug file, we wonder if there is a real problem :
Did the files have been correctly copied to your NT server or not ?

According to the debug informations, it seems that the job completed 
successfully, except for a 'cftp_close' error. You don't have to worry 
about this error (only due to the fact that the application tries to close 
a socket twice). This is just a warning and has no impact on the result of
the job.

If no file get copied on your NT server, could you generate another debug file on
this machine? The procedure is nearly the same as on Open VMS : declare an
environment variable called FTSO_DEBUG : you will obtain a file ftso_debug_srv_xxxx.log
(where xxxx is the process number) in the directory <install_path>\SYS\.
Be careful to reset this variable when you don't need it anymore, because your hard
disk will be full very quickly if you use ftso very often.

Regards

Christophe

Christophe,

I set up the debug option on the NT server and got a number of debug 
files. I can't see any problems with them. The files do get copied to the 
NT server ok. 

The whole process does appear to work in that the files do end up on the 
NT server my question was why does it still pass the 
username/password in clear text if its working ok. Would the settings 
on the FTP service affect the working of FTSO?

Thanks,

Gary

Gary,

>> The whole process does appear to work in that the files do end up on the 
>> NT server my question was why does it still pass the 
>> username/password in clear text if its working ok. Would the settings 
>> on the FTP service affect the working of FTSO?
???
I'm not sure to understand your question very well...
Let me remind you that FTSO is an application based on FTP so that every
file transfer is done via FTP.
And as the FTP protocol needs a username and password to work, it is the same
thing for FTSO (and clear password on the network is only due to the fact that
FTP doesn't encrypt this password).
Concerning the fact that the settings on FTP service affect the working of FTSO, 
I can say that if you can do a file transfer via FTP (with any settings you want),
it must be working with FTSO.

Hope this will be an answer to your questions
Christophe

Christophe,

I was originally pointed at this product by someone who is already using 
it and they thought that it uses encrypted passwords. I also noticed note 
89.6 in this conference which seems to support the fact that one of the 
benfits of layering FTSO on FTP was the use of encrypted passwords. Is 
this not the case?.

Thanks for your time in helping me get this resolved.

Gary

Gary,

FTSO is always using encrypted passwords on the client side :
* in every intermediate file used by the application
* in the alias files
that means you are not able to see clear passwords on this side.

Concerning the transmission of the password, you know the answer.

Regards

Christophe

Christophe,

Let me just make sure that I understand this:.

FTSO does not store the password in clear text on the client but when 
the it transfers data the password is passed as clear text.

Thanks,

Gary

Hi Gary,

>> FTSO does not store the password in clear text on the client but when 
>> it transfers data the password is passed as clear text.

Yes, you are right, the password is passed as clear text under :
	- the FTP protocol for file's transfers
	- the REXEC protocol for the remote post procedures 

Thanks,
Emmanuel.