[P2PSIP] Enrollment server handling base64 encoded csr parameter

"Michael Chen" <michaelc@idssoftware.com> Fri, 21 June 2013 17:08 UTC

MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_aa142345cd5e317df2d7fe2a788d0837"
To: Marc Petit-Huguenin <petithug@acm.org>
From: Michael Chen <michaelc@idssoftware.com>
Date: Fri, 21 Jun 2013 10:08:13 -0700
Message-Id: <20130621100813.59ca11a9ba9389561a029f06442e67fa.e623a2cc5a.mailapi@email03.secureserver.net>
User-Agent: MailAPI 24670
Cc: p2psip@ietf.org
Subject: [P2PSIP] Enrollment server handling base64 encoded csr parameter
Precedence: list

Hi Marc,
 
A bug in my program sent the following multi-part header followed by the pkcs10 DER binary, but your server ignored the transfer encoding header and processed the csr:
 
--0xD2454C4F
Content-Disposition: form-data; name="csr"
Content-Type: application/pkcs10
Content-Transfer-Encoding: base64
 
<CSR DER binary>
 
--0xD2454C4F


RFC2311 (referenced in section 11.3 of p2psip-base) does describe the use of base64 encoded application/pkcs10 content type (3.7.2). The p2psip-base draft should either endorse or explicitly exclude the base64 encoding stated in RFC2311.
 
Thanks
 
--Michael

[P2PSIP] Enrollment server handling base64 encode… Michael Chen
Re: [P2PSIP] Enrollment server handling base64 en… Marc Petit-Huguenin