If we use BIO_new_file(), on Windows it'll jump through hoops to work
around their brain-damaged charset/Unicode handling — it'll convert a
UTF-8 filename to UCS-16LE and attempt to use _wfopen().

If you use BIO_read_filename(), it doesn't do this. Shouldn't it be
consistent?

It would certainly be nice if SSL_use_certificate_chain_file() worked...

-- 
dwmw2

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to