diff options
author | Paul Kehrer <paul.l.kehrer@gmail.com> | 2018-07-10 04:55:02 +0530 |
---|---|---|
committer | Alex Gaynor <alex.gaynor@gmail.com> | 2018-07-09 19:25:02 -0400 |
commit | 20ae2c8084812bd218d2b1d2972774963c4d2041 (patch) | |
tree | b8d38879064f3cc0856b9771a08524d15925d15c /LICENSE.PSF | |
parent | 01c9dac7c0ac33fb3dd73ab32322f7fc1699c059 (diff) | |
download | cryptography-20ae2c8084812bd218d2b1d2972774963c4d2041.tar.gz cryptography-20ae2c8084812bd218d2b1d2972774963c4d2041.tar.bz2 cryptography-20ae2c8084812bd218d2b1d2972774963c4d2041.zip |
fix encoding BMPString in x509 name entries (#4321)
Previously we encoded them as UTF-8, but as best I can tell in reality a
BMPString is fixed-width basic multilingual plane big endian encoding.
This is basically UCS-2 (aka original Unicode). However, Python doesn't
support UCS-2 encoding so we need to use utf_16_be. This means you can encode
surrogate code points that are invalid in the context of what a
BMPString is supposed to be, but in reality I strongly suspect the sane
encoding ship has sailed and dozens if not hundreds of implementations
both do this and expect other systems to handle their nonsense.
Diffstat (limited to 'LICENSE.PSF')
0 files changed, 0 insertions, 0 deletions