Re: SSL Keyring file

Hello Chris and Scott,

Chris wrote:
>At V4R4 I don't have the GSKit, that I know of anyhow.

Scott wrote:
<RANT>

>This is one of the things I didn't like about the SSL APIs...  You
>shouldn't have to specify a keyring file.  You should register your app
>with the system registry, and then let the DCM assign which certificate
>resources you use.  It shouldn't be hardcoded in your programs!  You
>should be able to distribute your programs to other people's computers,
>and let them assign their own cert resources in DCM.  That's what DCM
>is for.

>This is fixed with GSKit.  That's one reason that GSKit is better.

</RANT>

That's what the SSL_Init_Application API is for.  It lets you initialize an
SSL session using a certificate associated with an application identifier.
You can use the Register Application for Certificate Use API to create an
application name, and then use DCM to associate a certificate with that
application name.

IIRC, SSL_Init_Application was new with 440.  Of course, I believe the
GSKit is intended to replace the SSL stuff anyway so you should consider
migrating to that, but if you are on 440, or need to support it, then
SSL_Init_Application will do the trick.

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------