Re: just curious... -- LINUX5250

Subject: Re: just curious...
From: Scott Klement <tn5250@xxxxxxxxxxxxxxxx>
Date: Mon, 23 Jul 2007 14:35:36 -0500
List-archive: <http://archive.midrange.com/linux5250>
List-help: <mailto:linux5250-request@midrange.com?subject=help>
List-id: Linux 5250 Development Project <linux5250.midrange.com>
List-post: <mailto:linux5250@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/linux5250>, <mailto:linux5250-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/linux5250>, <mailto:linux5250-request@midrange.com?subject=unsubscribe>

Hi Sean,

verify error:num=19:self signed certificate in certificate chain
verify return:0
22883:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake
failure:s3_pkt.c:1057:SSL alert number 40
22883:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake
failure:s23_lib.c:188:

When I try this on my own system (openssl s_client) I also get the "verify error" and "self signed certificate in chain" but it proceeds to work, regardless of that error.
I do not get the "alert number 40" error, however. A quick google search determines that "alert 40" means that the server and client weren't able to negotiate an acceptable set of security services. Does your system require a client certificate? Or does it require a certain size encryption key? or something like that?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: just curious... , Sean Porterfield

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.