Very old release, unsupported platform, closing ticket. Long live big iron!
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
: [openssl.org #1621] [PATCH] - OS390-Unix (EBCDIC) 0.9.7m
It's a bit disappointing, considering I first wrote those patches back in 2002.
It would be nice if someone could comment on what's preventing them from
getting incorporated.
JBYTuna wrote:
Richard,
Oh my. So, these patches have not been
JBYTuna wrote:
Oh my. So, these patches have not been incorporated? Will they ever get
incorporated?
I get once or twice a year this question, but every time i have to
answer: i don't know.
We did not know these patches existed. We've been chasing this problem for a
couple of years
On Fri, Dec 14, 2007, Richard Koenning wrote:
When i look at the long list of entries in
http://rt.openssl.org/NoAuth/Buglist.html i can understand, that the EBCDIC
patches don't have the highest priority for the OpenSSL team. Therefore the
best advice i can give is to use RT entry #843
It's a bit disappointing, considering I first wrote those patches back in
2002. It would be nice if someone could comment on what's preventing them from
getting incorporated.
JBYTuna wrote:
Richard,
Oh my. So, these patches have not been incorporated? Will they ever get
incorporated?
We
Richard,
Oh my. So, these patches have not been incorporated? Will they ever get
incorporated?
We did not know these patches existed. We've been chasing this problem for a
couple of years now. Because we've never received response to postings with
regard to this problem, we felt we were on
When an OpenSSL server built on z/OS is using client verification, the
following error is incurred:
0x140890b2 - error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no
certificate returned
From tracing, we found the correct certificate was being returned. We found
the code in
JBYTuna via RT wrote:
When an OpenSSL server built on z/OS is using client verification, the
following error is incurred:
0x140890b2 - error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no
certificate returned
From tracing, we found the correct certificate was being returned. We found
