Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90707
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.173 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <BE72BC98-B11C-4BDA-BC65-63BD1FDAEC80@heroku.com>
References: <CAGa2bXYJGdsfM4L=U0pWnqycC==r1tsqHtNOZcjG-nBGKAU_jA@mail.gmail.com>
 <BE72BC98-B11C-4BDA-BC65-63BD1FDAEC80@heroku.com>
Date: Tue, 19 Jan 2016 10:36:27 +0900
Message-ID: <CAGa2bXZErgEPFfqp_oEymMj85QiO0hRX3AL_Om45JA6huqX7JA@mail.gmail.com>
To: David Zuelke <dz@heroku.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Bug #68276 Reproducible memory corruption: pgsql
 conflicts with openssl extension
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

Hi David,

On Tue, Jan 19, 2016 at 2:31 AM, David Zuelke <dz@heroku.com> wrote:
>
> I have customers running into this too. I have not yet had time to pick up that patch - AFAICT, it's incomplete (see comments).
>
> We are, in parallel, working on getting a fix into libpq, but that's of course just a band-aid, since it can still happen with any other library that also uses openssl functions.

That's what I thought.

>
> The principle approach of that PR ("backing up" the errors from openssl) is good, though.

This issue is nasty. I hope you come up with feasible solution soon.

BTW, should I change the bug report category to openssl?

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net