Dear Andy, On Fri, Nov 20, 2015 at 12:08 PM, Andy Polyakov <[email protected]> wrote:
> > ... And on Windows it's even worse. As it stands now > > even passing non-ASCII strings as command-line argument [and presumably > > at prompt] is not an option. > > This is not entirely true. Whether or not one can pass non-ASCII strings > as command-line argument is language-specific. Or rather code > page-specific in Windowish. With Asian languages you're really out of > luck, while smaller alphabets can work out (but not mixed) if system > locale matches expectations. > I understand that there should be problems with Windows. So the test PKCS12 object was created using Windows using a GOST-providing CSP. I do not know whether the authors of the CSP have implemented their own mechanism of transforming the password or used any provided by the Windows system default. But in fact the openssl being built without defining the PBE_UNICODE macros was able to parse the test PKCS12. Thank you! -- SY, Dmitry Belyavsky
_______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
