From: [EMAIL PROTECTED]
n2xjk> OK, I got past the testca failure by making the following change to apps/ca.c:
n2xjk>
n2xjk> 1535a1536,1538
n2xjk> > #ifdef CHARSET_EBCDIC
n2xjk> > ascii2ebcdic(str->data,str->data,str->length);
n2xjk> > #endif
n2xjk>
n2xjk> There are still places where the display of information from
n2xjk> the certificate isn't translated to EBCDIC, but this at least
n2xjk> gets past the check. Now the test suite runs to completion.
That's not very smart as a general thing. str->data points somewhere
right into the request and your code makes changes right into that
request, which makes it suddenly unusable for further processing. Or
so I gather from readin the source...
The quickest fix would be to do a transform of charset inside the
printing loop (around line 1594) in a temporary variable.
What would really need to be done would be to specify very exactly
where native charsets get in, that they get converted to ASCII there,
where native charsets get out, and that internal (ASCII) strings
should be converted to EBCDIC at those points.
The goal would be to keep it all ASCII (or ISO-8859-1) inside OpenSSL
and simply have some kind of "charset firewall" at known points.
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
