T
Tai Li
Guest
Tried http://knowledgebase.progress.com/articles/Article/P90739 , with a different results, it looks positive: Loading 'screen' into random state - done CONNECTED(00000160) depth=1 /C=SG/ST=SG/L=SG/O=NONE/OU=NONE/CN=NONE/emailAddress=NONE verify return:1 depth=0 /C=SG/ST=SG/O=NONE/OU=NONE/CN=NONE verify return:1 --- Certificate chain 0 s:/C=SG/ST=SG/O=NONE/OU=NONE/CN=NONE i:/C=SG/ST=SG/L=SG/O=NONE/OU=NONE/CN=NONE/emailAddress=NONE -----BEGIN CERTIFICATE----- MII... MAk... DAR... MDI... BAg... T05... ftA... 98t... 6De... DQQ... Lsp... wcc... AYY... ynd... g4E... -----END CERTIFICATE----- --- Server certificate subject=/C=SG/ST=SG/O=NONE/OU=NONE/CN=NONE issuer=/C=SG/ST=SG/L=SG/O=NONE/OU=NONE/CN=NONE/emailAddress=NONE --- No client certificate CA names sent --- SSL handshake has read 829 bytes and written 316 bytes --- New, TLSv1/SSLv3, Cipher is AES128-SHA Server public key is 1024 bit Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher : AES128-SHA Session-ID: D71... Session-ID-ctx: Master-Key: 7B79... Key-Arg : None Start Time: 1392713802 Timeout : 300 (sec) Verify return code: 0 (ok) --- read:errno=10054 Ran the Progress client, different error message this time: Secure Socket Layer (SSL) failure. error code -55: CONNECT HostName: ( host name ) does not match Certificate: ( host name beginning with * ) (9318) Implemented "-nohostverify" argument from http://knowledgebase.progress.com/articles/Article/P128646 to the Progress client but still having the same error message. Any advise?
Continue reading...
Continue reading...