Am 14.04.20 um 14:57 schrieb K Lengauer:
Hi Stephan,
Thank you for your quick response and also the link to your github issue. I
must have brushed over it when searching for similar issues, apologies.
Anyway, this seems to further confirm the issue(s) at hand...
Did you have any success or have
Hi ,
we are trying to add tls support to socks proxy with Curl as part of that
we are trying to complete initial TLS handshake.
we are trying to run openssl s_server on loopback interface to verify
changes
we tried two methods both are resulting in fatal error alert from server.
Method 1 - use exi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The OpenSSL project team would like to announce the forthcoming release
of OpenSSL version 1.1.1g.
This release will be made available on Tuesday 21st April 2020 between
1300-1700 UTC.
OpenSSL 1.1.g is a security-fix release. The highest severity i
Hi Stephan,
Thank you for your quick response and also the link to your github issue. I
must have brushed over it when searching for similar issues, apologies.
Anyway, this seems to further confirm the issue(s) at hand...
Did you have any success or have you made any attempts at fixing this so
far
Hello Kevin,
Am 14.04.20 um 10:00 schrieb K Lengauer:
Dear all,
I want to add another issue that occurred to me and would appreciate some
input from others using zOS OpenSSL.
Calls like "ossl_isascii(c)" such as is done in "a_print.c" in method "int
ASN1_PRINTABLE_type(const unsigned char *s,
Dear all,
I want to add another issue that occurred to me and would appreciate some
input from others using zOS OpenSSL.
Calls like "ossl_isascii(c)" such as is done in "a_print.c" in method "int
ASN1_PRINTABLE_type(const unsigned char *s, int len)" lead to wrong behavior
for me on zOS if the in
