On Feb 5, 2008, at 3:55 PM, Miguel Delapaz wrote:
The control port has to be secure before you can use PRIVATE to
secure the data port. You can issue CPROTECT to secure the control
connection on the fly. Alternately, use the SECURE option on the FTP
command, or take a look at the SECURECONTROL and SECUREDATA
statements in the FTP DATA file.
ftp localhost (secure
VM TCP/IP FTP Level 530
Connecting to LOCALHOST 127.0.0.1, port 21
220-FTPSERVE IBM VM Level 530 at SNAVM3, 18:09:07 EDT TUESDAY 2008-02-05
220 Connection will close if idle for more than 5 minutes.
>>>AUTH TLS
234 Security data exchange complete
Unable to secure control connection: (2001) Certificate error checking
is not va
lid for self-signed certificates
Well, poo!
Adam
