-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling non-ASCII output #458
Comments
We have 2 approaches to deal with Unicode in X.509 extensions:
The 1st approach looks more reasonable to me |
OTC: We prefer the second option unless it becomes too invasive @beldmit to investigate further |
We have the For a particular known extension we get a i2s callback from the Then At a first glance the naturally looking extension to implement this is AKID that can contain the Issuer field. I didn't find anything else from the list of currently supported extensions. |
Here we have the definitions of the flags Not null value is set only in AKID, v3info, crldp, issuer sign tool, Thawte strong extranet - and all of them use MULTILINE flag. So the solution may be copy the |
AI @beldmit to create an RFE issue in openssl/openssl describing the specification of how this should be implemented. |
Done, feel free to adjust my best English :) |
There is an issue to be worked on. Nothing for OTC to track anymore. Closing. |
See openssl/openssl#3291
The text was updated successfully, but these errors were encountered: