openssl

wbrawner/openssl

Fork 0

Commit graph

Author	SHA1	Message	Date
Andy Polyakov	fb5d9f1db5	Windows: UTF-8 opt-in for command-line arguments and console input. User can make Windows openssl.exe to treat command-line arguments and console input as UTF-8 By setting OPENSSL_WIN32_UTF8 environment variable (to any value). This is likely to be required for data interchangeability with other OSes and PKCS#12 containers generated with Windows CryptoAPI. Reviewed-by: Richard Levitte <levitte@openssl.org>	2016-08-25 11:56:28 +01:00
Andy Polyakov	4e155ec47e	apps/openssl.c: UTF-y Windows argv. Windows never composes UTF-8 strings as result of user interaction such as passing command-line argument. The only way to compose one is programmatic conversion from WCHAR string, which in turn can be picked up on command line. [For reference, why not wmain, it's not an option on MinGW.] Reviewed-by: Richard Levitte <levitte@openssl.org>	2016-08-01 09:52:06 +02:00

Author

SHA1

Message

Date

Andy Polyakov

fb5d9f1db5

Windows: UTF-8 opt-in for command-line arguments and console input.

User can make Windows openssl.exe to treat command-line arguments
and console input as UTF-8 By setting OPENSSL_WIN32_UTF8 environment
variable (to any value). This is likely to be required for data
interchangeability with other OSes and PKCS#12 containers generated
with Windows CryptoAPI.

Reviewed-by: Richard Levitte <levitte@openssl.org>

2016-08-25 11:56:28 +01:00

Andy Polyakov

4e155ec47e

apps/openssl.c: UTF-y Windows argv.

Windows never composes UTF-8 strings as result of user interaction
such as passing command-line argument. The only way to compose one
is programmatic conversion from WCHAR string, which in turn can be
picked up on command line.

[For reference, why not wmain, it's not an option on MinGW.]

Reviewed-by: Richard Levitte <levitte@openssl.org>

2016-08-01 09:52:06 +02:00

2 commits