I actually ended up solving it by removing all uses of BIO_new_fp() in
favor of my own custom BIO that I just finished writing earlier this
week.
Why not BIO_new_file?
Yeah, I discovered while analyzing the code that using BIO_new_file()
rather than BIO_new_fp() would disengage applink, however that was not
an option for me because BIO_new_file() can't open a file whose name
contains non-ANSI Unicode characters on Windows. I have to open the
file myself using _wfopen().
There was suggestion to fall back to wfopen from a vmware engineer a
while ago, but he couldn't provide patch (not that it would be very
complex) and it was not followed up. Idea must have been something
similar to just committed http://cvs.openssl.org/chngview?cn=19610.
Please note that it's *not* like I disapprove practice of custom BIO and
suggest you to abandon it. It's *not* like that. On the contrary I can
appreciate advantage and even say that it's better approach than one
suggested in the beginning of the thread. A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
