I'm surprised by how little seems to need changed. Is that really
possible? I imagined the EBCDIC issue was a much bugger can of worms.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
[EMAIL PROTECTED] \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN
> I vote for including the patch into mainstream OpenSSL. I repeat the
> ('@'-fixed) Howard Chu EBCDIC patch in this mail because the version
> from http://www.openldap.org/faq/index.cgi?file=745 does not
> apply cleanly (HTML-escapes present).
Oops - I fell into the same trap (HTML-frontends for
Latest openssl-0.9.7a:
A call of 'openssl x509 -text -in blah.pem' gets an
unsightly print of the X509v3 extensions.
Name and value of a v3 extension puts in the same
column without indent.
I made a cosmetic change in crypto/x509v3/v3_prn.c:
Index: v3_prn.c
===
Hi
I 've compiled "openssl-0.9.7a" on HPUX 11.20 (aka IA64) platform.
In order to do that I had to make the following changes.
1- HPUX-IA64 likes ".so" library rather than ".sl", although it will load the
".sl".
2- I 've made following changes:
Configure:
atlantis<7> diff Configure Configur
> -Original Message-
> From: Martin Kraemer [mailto:[EMAIL PROTECTED]
> Hello Howard, hello OpenSSL developers,
Hello!
> At
> http://www.openldap.org/faq/index.cgi?file=745
> you print the set of patches to OpenSSL, and I verified them to work
> on our BS2000 version of OpenSSL as well
> Date: Fri, 28 Feb 2003 13:34:41 -0800
> From: Howard Chu <[EMAIL PROTECTED]>
> Subject: RE: EBCDIC
>
> I ported OpenLDAP, OpenSSL, Berkeley DB 4.1, and part of Cyrus SASL to
> OS/390. Aside from Cyrus, all of these packages were fully functional but
> OpenLDAP and OpenSSL operate with ASCII inte
