I could not get PCOMM to connect through an SSLSERV with a self-signed
certificate. When I got my real certificate from the authorities, it worked
fine. To connect with our OS/390 system something else had to be done about
adding some intermediary's cert to the database. I can check on that for you if
you want. The x3270 package from State of Alaska worked fine against the
self-signed SSLSERV.
/Tom Kern
/301-903-2211
--- Dave Jones <[EMAIL PROTECTED]> wrote:
> Hi, gang.
>
> Does anybody have a working example of using PCOMM 5.8 (on windows XP)
> making a secure SSL connection to a VM host that has the SSLSERV server
> installed that they would be willing to share?
>
> So far, I have done the following:
>
> 1) installed the SSL Server, per IBM instructions. It starts up as expected.
> 2) created a self signed certificate, using:
> SSLadmin SELF filename A 512 label
> where filename has the X509INFO data, that I created myself. "label" is
> an 8 character label name. SSLSERV accepts this command without problem.
> The SSLESERV is restarted to pick up the change.
> 3) update the PROFILE TCPIP file to allow for SSL protection on port
> xxxxx for TN3270 access.
> PORT
> xxxxx TCP INTCLIEN SECURE label ; TELNET Server
> where "label" is the same as the label given in step 2. TCPIP is restarted.
> 4) an SSLADMIN QUERY CERT * does show the self signed certificate as
> being in the database.
> 5) I have downloaded to my Windows XP workstation the "filename
> X509CERT" file that is output by step 2. I have converted the base
> 64-encoded file to a purely binary one.
>
> Now I'm stuck.....how to I get PCOMM to connect to the VM host, using my
> self signed certificate? Any help gratefully appreciated.
>
> Have a good one, to.
>
> --
> Dave Jones
> V/Soft Software, Inc.
> Houston
> 281.578.7544
__________________________________
Yahoo! Music Unlimited
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/
