RE: FTPAPI new SSL support (READY status)

["Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>]

Sender: "Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>

SSL support would be a good thing for us. We're still at V5R1 at the moment,
because we need to get some processes off of Office Vision (yes, I know),
and then we can upgrade to V5R3 or V5R4.

I could use the SSL support to automate a process that has to be done
manually right now.

I'll be watching for when that version comes out. 

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 



-----Original Message-----
From: owner-ftpapi@xxxxxxxxxxxxx [mailto:owner-ftpapi@xxxxxxxxxxxxx] On
Behalf Of craigs@xxxxxxxxx
Sent: Tuesday, April 25, 2006 1:17 PM
To: ftpapi@xxxxxxxxxxxxx
Subject: FTPAPI new SSL support (READY status)

Sender: craigs@xxxxxxxxx


I have changed FTPAPI 2.2 to have FTP SSL support.  Scott, I can give you
what I have if you wish so you can integrate it into a new version.  Or, you
can give me what you have been working on and I can integrate it.  It
doesn't take too long.  I have tested doing GETs, MGETs, and PUTs both using
SSL and non-SSL.  PORT connections (non-passive) connections used for
communicating data back and forth will probably not work with SSL.  Only
passive.  But, that is the default on the recent IBM FTP client >= V4R2M0.
Also, I added the bonus of defaulting to passive mode if the operating
system is release >= V4R2M0 and QUSRSYS/QTMFTPPASV doesn't exist (like the
IBM FTP client).  Of course, using the ftp_passivemode can override the
default.
The only thing programs need to do to implement SSL once in the new version
is to call procedure ftps_init() just like https_init() from HTTPAPI.  You
should also test for init errors and call the ftps_dcm_reg() just like
https_dcm_reg().  With the passive default, you should probably never have
to call the ftp_passivemode.  ftps_cleanup() is there like https_cleanup()
but will probably be normally unused due to closing on activation group
close.  There is a new ex8urlssl to show this.

I should add a disclaimer that even though I have tested this, I don't
guarantee its results.  I just added a gskssl_h and errno_h copy members, I
added code to ftpapir4, and ftpapi_h.  Oh, also, the ftpapi_x binder source.

Scott, please let me know what you want to do.  I can email you the save
file with my library to the email address you specify.  I tried to focus on
changing as little as possible.  All my changes have the date 4/24/06.  I
would feel better if you could look over what I did to make sure I didn't
miss anything.  Yes, I could have put some of that stuff into modules.
But, I see that in your changelog to do list.  Something about setting it up
so users could add their own communication methods, etc.

Craig Strong

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail to
majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------