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.
Regards, Miguel Delapaz z/VM TCP/IP Development The IBM z/VM Operating System <[email protected]> wrote on 02/05/2008 01:20:06 PM: > I have SineNomine's SSLSERV installed on my z/VM 5.3 system and I can > establish secure telnet sessions. I tried to configure FTP to take > advantage of SSL as well. In SRVRFTP CONFIG, I specified TLSLABEL > Y2KVM07, the certificate in the SSLSERV database, SECURECONTROL ALLOWED > and SECUREDATA ALLOWED. Is that all that is required or do I need a > different FTP service machine? Will the IBM FTPSERVE establish a secure > connection. If so, how do I tell it to do so? I entered PRIVATE after > an FTP session had been established between a couple of test systems, > both of which have SSLSERV installed but got back the following > message. This is what I got when I issued PRIVATE on the client end of > an FTP session: > > /Command: > private > Control connection is not secure > / > Do I need to specify a control port for FTPSERVE with the SECURE keyword > and the certificate name? > > Jim > > -- > Jim Bohnsack > Cornell University > (607) 255-1760 > [EMAIL PROTECTED]
