diff options
| author | Andrew Bennett <[email protected]> | 2013-11-07 16:11:21 -0700 |
|---|---|---|
| committer | Andrew Bennett <[email protected]> | 2013-11-07 17:11:35 -0700 |
| commit | ef6922881585771ecb9d934cf01f9f1f8ad62211 (patch) | |
| tree | 744b967fc8456571ecc4f4b8424391da46f00832 /erts | |
| parent | 768a64354e3d69b3c0840a84dd072601c67ca39d (diff) | |
| download | otp-ef6922881585771ecb9d934cf01f9f1f8ad62211.tar.gz otp-ef6922881585771ecb9d934cf01f9f1f8ad62211.tar.bz2 otp-ef6922881585771ecb9d934cf01f9f1f8ad62211.zip | |
public_key: Workaround for incorrectly encoded utf8 emailAddress
Author: Daniel Barney <[email protected]>
Date: Thu Oct 25 14:33:11 2012 -0600
Most common browsers are lax in thier handling of how the
emailAddress field is encoded. RFC 3280 section 4.1.2.6
defines the encoding as IA5String, however browsers will
also handle certificates with the emailAddress field
encoded as UTF8String. This fix allows the emailAddress
to be decoded as both an IA5String and an UTF8String.
Reviewed by: Andrew Bennett <[email protected]>
Diffstat (limited to 'erts')
0 files changed, 0 insertions, 0 deletions