Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107760
MIME-Version: 1.0
References: <CAOwTYAsyi1ahiRBaWcqs5HEiRCNfVQz3MirTB0Qu39v2ivz6ng@mail.gmail.com>
 <7fc5347c-a634-0b68-8b2b-95be6f7d2ce4@gmx.de>
In-Reply-To: <7fc5347c-a634-0b68-8b2b-95be6f7d2ce4@gmx.de>
Date: Mon, 4 Nov 2019 09:33:00 +0100
Message-ID: <CAOwTYAuFU-sF59bjbyLPXHoFmjh1tjb-uL=HToMSskEt9Po=AA@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007e61720596812a54"
Subject: Re: FFI & Security
From: krakjoe@gmail.com (Joe Watkins)

--0000000000007e61720596812a54
Content-Type: text/plain; charset="UTF-8"

Morning internals,

Sorry about the delay, this has now been updated.

> There was an unexpected problem communicating with SMTP: Unexpected
return code - Expected: 250, Got: 451 | 451 4.3.0 Error: queue file write
error

Because infrastructure ...

Cheers
Joe

On Wed, 30 Oct 2019 at 12:41, Christoph M. Becker <cmbecker69@gmx.de> wrote:

> On 14.10.2019 at 09:44, Joe Watkins wrote:
>
> > Recently we voted on classification criteria for security bugs [1], we
> > include under "not an issue" any issue that "requires invocation of
> > specific code, which may be valid but is obviously malicious".
> >
> > I would like to add an explicit clause under the "not an issue" section
> for
> > anything related to FFI.
> >
> > It hardly seems worth it to run an RFC, although I'll be happy too if
> there
> > is a single dissenting voice.
> >
> > If there are no objections, I'll modify the document 7 days from today
> > (Monday 21st October).
> >
> > Cheers
> > Joe
> >
> > [1] https://wiki.php.net/security
>
> What is the status here?  It seems the security classification document
> has not yet been updated.
>
> Cheers,
> Christoph
>

--0000000000007e61720596812a54--