One Willie Gallant - presumably ([email protected]) - posted the following so that it appeared in Google Groups but *not* in the IBM-MAIN archives. He is, of course, directed to the standard text following the quoted post where he will discover how to reach his full intended audience.
If you're attempting to ftp/ssl using a batch job, you need to add -a after the IP address...i.e. xxx.xxx.xxx.xxx. -a At this point even if you have ftp.data parameters setup correctly and get AUTH TLS and Negotiation Successful, does not guarantee encryption worked. It will default to raw ftp if it didn't get encrypted. It's not so difficult if you ftps out with limited firewalls and NAT IPs. On Jun 16, 5:35 am, [email protected] (Marco Gianfranco Indaco) wrote: > *" That is, the process may go on and pick a 'security mechanism'." *Depends on ftpd configuration and what you mean with "secure transfer"(still talking about ftp and not network tricks) If you need a secure login that is often used for secure transfer you cannot pick a security mechanism after ftpOpen. You can receive a message like:* 530 Have to use explicit SSL/TLS before logging on. * For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives athttp://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
