×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Last night I configured a new v6r1 machine to use SSL. I configured a
2048 bit key. Today x5250 fails to connect using SSL about 50% of the
time. A tracefile shows that the certificate was successfully verified.
However, soon after validating the certificate it appears that lib5250
simply drops the connection. The reason it appears this was is because
the trace file is very short. Here it is in its entirety:
tn5250_ssl_stream_init() entered.
SSL Method = SSLv23_client_method()
tn5250_ssl_stream_init() success.
tn5250_ssl_stream_connect() entered.
Connected with SSL
Using AES128-SHA cipher with a 128 bit secret key
SSL Certificate issued by: (I cut this stuff out from the trace)
SSL Certificate successfully verified!
SSL must be Non-Blocking
tn5250_ssl_stream_connect() success.
tn5250_dbuffer_clear_table() entered.
tn5250_char_map_new: map = "37"
Macro: fname=/home/james/.tn5250macros
I'll try and do some debugging on this later, but I wanted to check if
anyone has had a similiar problem with v6r1 or not before I spent too much
time on this. This problem occurs whether I'm on the local LAN or outside
the firewall, so it doesn't appear to be related to network configuration
issues. The really strange part is that it fails like this about half the
time. Non-SSL connections always work perfectly. Ideas?
James Rich
if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.