Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110127 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 14996 invoked from network); 11 May 2020 11:23:05 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 May 2020 11:23:05 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id DA9BA1804C4 for ; Mon, 11 May 2020 02:59:29 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,SPF_PASS, T_SPF_HELO_PERMERROR autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS51395 185.32.220.0/22 X-Spam-Virus: No X-Envelope-From: Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 11 May 2020 02:59:29 -0700 (PDT) Received: from [10.61.171.85] ([173.38.220.37]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-10) with ESMTPSA id 04B9xRE5060381 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Mon, 11 May 2020 11:59:28 +0200 Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1589191168; bh=bT1WSF9FTvcNSov3ysCjP0ztKgoidyrPNYcYUl4ciNU=; h=To:From:Subject:Date:From; b=bht9lM7sN9H5AYUnj2l+4PoeB2p5I2gerV4MBuQzgIou40jzUcg8LBfbf9wPMVFTE SMB1E1hzkLN636hynilshp1JRPqHUgLJPxOj/mLlLkC/yRXMFfP1qzb5xMOTnBx1p5 lJU5W2nGYCh5tBoLGj8IEYvhS3oEw2yrgPinLlD0= To: internals@lists.php.net Autocrypt: addr=lear@lear.ch; prefer-encrypt=mutual; keydata= mQENBFMe1UQBCADdYOS5APDpIpF2ohAxB+nxg1GpAYr8iKwGIb86Wp9NkK5+QwbW9H035clT lpVLciExtN8E3MCTPOIm7aITPlruixAVwlBY3g7U9eRppSw9O2H/7bie2GOnYxqmsw4v1yNZ 9NcMLlD8raY0UcQ5r698c8JD4xUTLqybZXaK2sPeJkxzT+IwupRSQ+vXEvFFGhERQ88zo5Ca Sa1Gw/Rv54oH0Dq2XYkO41rhxQ60BKZLZuQK1d9+1y3I+An3AJeD3AA31fJZD3H8YRKOBgqe ILPILbw1mM7gCtCjfvFCt6AFCwEsjITGx55ceoQ+t5B5XGYJEppMWsIFrwZsfbL+gP31ABEB AAG0GUVsaW90IExlYXIgPGxlYXJAbGVhci5jaD6JAU4EEwECADgCGwMCHgECF4AWIQSY0L2Q Rh2wkqeyYR2HtmtG2dJ6MwUCWxJwMwULCQgHAgYVCAkKCwIEFgIDAQAKCRCHtmtG2dJ6M8KI B/46pFrJX+4Ockl2fHR303ais9Lyx8jv6mXKKOr8WR0UYcJ0syQrhaaZNG1VV98tYQHHK9F5 y7hH4YCsrr3odZ6zoavnx5X1X/2xw8y732f/irVoOOkYLid9IGPxa2e2nYXCZpde5/yvv3we XVE4mG4dEAD5T8iKS4Hz/3fKGJQ15o79Jv92HgC7RpCt0WaiQ0b6acP3PuwjDJzJzLFZzb7j IiB3izxQESSWE1GNRmoAK/k0gW6kmx1/87tQENrK+3Nn4CJSFQWF6entLnY7UeVm95wbMQkJ evwddDWUO2huDbmZnmxgKXGzSSpuNq7n8ICAOlbt0HfdJAZQfy25bwveuQENBFMe1UQBCAC0 WV7Ydbv95xYGPhthTdChBIpPtl7JPCV/c6/3iEmvjpfGuFNaK4Macj9le20EA5A1BH7PgLGo HOiPM65NysRpZ96RRVX3TNfLmhGMFr5hPOGNdq+xcGHVutmwPV9U7bKeUNRiPFx3YdEkExdd qV2E8FltT0x2FSKe2xszPPHB6gVtMckX5buI9p1K3fbVhXdvEkcYY/jB0JEJGyhS5aEbct5c HUvDAkT81/YFK5Jfg8RRwu1q1t1YuIJSOWAZQ9J9oUsg6D9RpClU+tIFBoe3iTp1AUfJcypu cGKgLYKtpu/aygcpQONHYkYW5003mPsrajFhReVF5veycMbHs4u5ABEBAAGJAR8EGAECAAkF AlMe1UQCGwwACgkQh7ZrRtnSejOSuQgA27p2rYB7Kh20dym6V8c62pWpBHHTgxr/32zevxHS iXl6xvUCg5T8WUwfUk8OvgDcBErK/blDAMXQzSg3sp450JhR8RnXHXF5Zz2T04X7HnlIVJGw f2CjnwyEAJCqMzaCmI+g3Imvg/8L4nyBFvhlFHDv+kIvMiujyycjPAu7xxKplBs1/IEwmDoA MjneFmawvfeQnwdMhSKK8PjKSuzGU5uUmxj3GBfRqvTM0qpmhMPFOmDhJSmH55HLAky2Mlmq JYXJPt/9EfSEhFiua1M6gLiuNEuPkp+8jcnHQqKr0IeHt8UqcwLt2mGfIyl0FVdF9hvWPjNR zGbgqoT1Di03RQ== Message-ID: Date: Mon, 11 May 2020 11:59:27 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mzk1ivUhn7b59dJJX3gUn7rx8OdDE3rTL" Subject: PR #5251 adds support for CMS (RFC5662) From: lear@lear.ch (Eliot Lear) --mzk1ivUhn7b59dJJX3gUn7rx8OdDE3rTL Content-Type: multipart/mixed; boundary="0nqjWNwn0enqsmeZh9DzK3q4L7C84XkeT" --0nqjWNwn0enqsmeZh9DzK3q4L7C84XkeT Content-Type: multipart/alternative; boundary="------------DF0C3A491EBE9371DB04283C" Content-Language: en-US This is a multi-part message in MIME format. --------------DF0C3A491EBE9371DB04283C Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi everyone, I am new to the PHP development process, so please forgive me if I have this wrong. In PR #5251[1] I=E2=80=99ve created OpenSSL CMS functions that are nearly= direct analogues to the openssl PKCS#7 functions.=C2=A0 Cryptographic Message Sy= ntax is defined in RFC 5652[2], and is a follow-on to PKCS#7.=C2=A0 These functions are useful to developers who are creating or verifying PKI-based signatures (this is the case for me or anyone else who is implementing or deploying RFC 8520[3]), and there are other IoT services that are using CMS as well (not to mention certain modern mailing systems= ). There are one or two changes- one can specify the encoding format as an argument, for instance, and error out out the use of DETACHED with S/MIME encoding, as nobody seems to know what that would mean. I=E2=80=99ve been working with Jakub and others who have been very genero= us with their time on code reviews.=C2=A0 I would be grateful for any additional feedback you would have, with an eye toward merging this PR.=C2=A0 The PR= is already marked as RFC I have not yet formalized that.(*) Best regards, Eliot (*) I tried adding an RFC page on the wiki, but sensibly, as I just created the account, the system did not permit me to do so. [1] https://github.com/php/php-src/pull/5251 [2] https://www.rfc-editor.org/rfc/rfc5652.html [3] https://www.rfc-editor.org/rfc/rfc8520.html --------------DF0C3A491EBE9371DB04283C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi everyone,=

I= am new to the PHP development process, so please forgive me if I have this wrong.
<= br>
I= n PR #5251[1] I=E2=80=99ve created OpenSSL CMS functions that are= nearly direct analogues to the openssl PKCS#7 functions.=C2=A0 Cryptographic Message Syntax is defined in RFC 5652[2], and is a follow-on to PKCS#7.=C2=A0 These functions are useful to developers who are creating or verifying PKI-based signatures (this is the case for me or anyone else who is implementing or deploying RFC 8520[3]), and there are other IoT services that are using CMS as well (not to mention certain modern mailing systems).
<= br>
T= here are one or two changes- one can specify the encoding format as an argument, for instance, and error out out the use of DETACHED with S/MIME encoding, as nobody seems to know what that would mean.
<= br>
I= =E2=80=99ve been working with Jakub and others who have been very generous with their time on code reviews.=C2=A0 I would be grateful for = any additional feedback you would have, with an eye toward merging this PR.=C2=A0 The PR is already marked as RFC I have not yet formalized that.(*)
<= br>
B= est regards,
<= br>
E= liot
<= br>
(= *) I tried adding an RFC page on the wiki, but sensibly, as I just created the account, the system did not permit me to do so.
<= br>
[3] https://ww= w.rfc-editor.org/rfc/rfc8520.html
--------------DF0C3A491EBE9371DB04283C-- --0nqjWNwn0enqsmeZh9DzK3q4L7C84XkeT-- --mzk1ivUhn7b59dJJX3gUn7rx8OdDE3rTL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAl65If8ACgkQh7ZrRtnS ejN9Ggf8DK3VrTqjvevT+IqBZ43/d5aCnksTAz7DuVjea9tYMjlOr2ZusEQjLOQC dnnl0pxbQ1k5OMHt0MmtGH92/wBA+ayfNASWDCESkGNTBvm9NtGl2WmXF7Q7/R4L XLPGih0AYVrC4GqEtEMtnfT+/8BzlQ+MFAAatZ2GJtP8kiDe2A0ksk1qIBar87hu M4uqdnWDs9PLdkZ4SpXrAfIcr5P8GLs3nZ9y9bBVqKjW7kZBArtBSIyjtCOAF0KY WPFW2Wb79D2kY7xAxJiAHlDVBo8R9KYR4KObmXQG770Xw8Ws04+yU2mt7f0rd6MO B8rXJCxK8RkyanzROevA6XuTb6vosQ== =d8Yd -----END PGP SIGNATURE----- --mzk1ivUhn7b59dJJX3gUn7rx8OdDE3rTL--