We're using the binary distributions from Shining Light for Windows compiling with Borland C++ Builder 6.0 , the source version from OpenSSL.org for Linux. Linux works peachy.... the applink bit (which is a pain) but eventually that all seems sorted. PEM_read_X509 still crashes. ... So I have my own copy of "int file_gets(BIO *bp, char *buf, int size)" and before I call PEM_read_X509 I say; BIO_s_file()->bgets = file_gets; and now instead of crashing, the certificate loads fine. The only alteration is that now "file_gets" lives in the app instead of the statically linked library. My question is, is this part of some known issue that I've missed finding the documentation for?
No, it's a bug: applink was not enganged for that particular call. See http://cvs.openssl.org/chngview?cn=14467 for fix.
Or is this some sort of bizarre effect of the Borland link/calling conventions?
But there is no guarantee that there no bizarre effects left. As far as I understand above mentioned binary distribution is built with Visual C and then Borland libs are obtained by format converting utility, presumably coff2omf. A.
______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
