]> git.ipfire.org Git - thirdparty/strongswan.git/commit
pki: Always and implicitly use base64 encoding for EST requests/response
authorMartin Willi <martin@strongswan.org>
Tue, 20 Sep 2022 05:47:25 +0000 (07:47 +0200)
committerAndreas Steffen <andreas.steffen@strongswan.org>
Tue, 20 Sep 2022 09:07:33 +0000 (11:07 +0200)
commita708e969068b32a5abb07bd325de19f6670109f6
tree3b5099ec47f153a5b5c9d0f478ad63d76637965f
parent75d820de8bfb556f96463f020500fe6884f0568b
pki: Always and implicitly use base64 encoding for EST requests/response

Content-Transfer-Encoding is actually not a valid HTTP header, but a MIME
header, and must not be used. The original RFC7030 specifies this wrong,
and an errata discusses this issue.

The use of base64 encoding has been clarified in RFC8951, and the
recommendation is to always use/expect base64 encoding, but not send/expect
the Content-Transfer-Encoding header.
src/pki/est/est_tls.c