Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110147
MIME-Version: 1.0
References: <fcccdf25-b1f1-a2c7-ffc9-2a19f04ecf38@lear.ch> <8c7f1f4d-e12f-7bd6-73e8-a491937e46b2@gmx.de>
In-Reply-To: <8c7f1f4d-e12f-7bd6-73e8-a491937e46b2@gmx.de>
Date: Tue, 12 May 2020 17:10:10 +0200
Message-ID: <CAFPFaM+dg6B=Zfq5jSGwKpw1+AE+WDR6axMZpx43UvBBbV_+Ow@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: Eliot Lear <lear@lear.ch>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f4035e05a574dc75"
Subject: Re: [PHP-DEV] Re: PR #5251 adds support for CMS (RFC5662)
From: george.banyard@gmail.com ("G. P. B.")

--000000000000f4035e05a574dc75
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 11 May 2020 at 12:45, Christoph M. Becker <cmbecker69@gmx.de> wrote=
:

> On 11.05.2020 at 11:59, Eliot Lear wrote:
>
> > 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 near=
ly direct
> > analogues to the openssl PKCS#7 functions.  Cryptographic Message Synta=
x
> > is defined in RFC 5652[2], and is a follow-on to PKCS#7.  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 service=
s
> > 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 gene=
rous with
> > their time on code reviews.  I would be grateful for any additional
> > feedback you would have, with an eye toward merging this PR.  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
>
> Thanks for working on CMS support!
>
> I have granted you RFC karma.  Best of luck with the RFC. :)
>
> --
> Christoph M. Becker
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Does this really require an RFC?
This seems like just exposing some underlying functionality from OpenSSL
to userland which I wouldn't have expected to need an RFC to be added.

Best regards

George P. Banyard

--000000000000f4035e05a574dc75--