97a33939a3
The IUF functions were added for PEM and internally are very lenient to whitespace and include other PEM-specific behaviors (notably they treat hyphens as EOF). They also decode a ton of invalid input (see upstream's RT #3757). Upstream has a rewrite with tests that resolves the latter issue which we should review and import. But this is still a very PEM-specific interface. As this code has basically no callers outside the PEM code (and any such callers likely don't want a PEM-specific API), it's probably not worth the trouble to massage this and PEM into a strict IUF base64 API with PEM whitespace and hyphen bits outside. Just deprecate it all and leave it in a corner. Change-Id: I5b98111e87436e287547829daa65e9c1efc95119 Reviewed-on: https://boringssl-review.googlesource.com/5952 Reviewed-by: Adam Langley <agl@google.com> |
||
---|---|---|
.. | ||
openssl |