Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.lang.php
Subject: Re: Heartbleed bug?
Date: Thu, 10 Apr 2014 08:51:23 +0200
Lines: 24
Message-ID: <53463F6B.5010406@arnowelzel.de>
References: <38941292-a3a7-4dc0-ba31-873351d81924@googlegroups.com>     <li3h9p$ab4$1@dont-email.me> <VaadncnjeJs3zNjOnZ2dnUVZ_gmdnZ2d@giganews.com> <li3oid$2up$1@dont-email.me> <53456ab0$0$6618$9b4e6d93@newsspool4.arcor-online.net> <li40fs$8bs$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: individual.net to/D1Rf6IVAyrZZwoLp6eQbI0uBPTr9KtmSXhCm80bNMJ+3rKl
Cancel-Lock: sha1:efk0YritsVNBFuFXmuFGuuEATjs=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
In-Reply-To: <li40fs$8bs$1@dont-email.me>
X-Enigmail-Version: 1.6
Xref: csiph.com comp.lang.php:13368

Jerry Stuckle, 2014-04-09 19:37:

> On 4/9/2014 11:43 AM, Christoph Michael Becker wrote:
[...]
>> ACK.  However, the Windows x86 builds of PHP 5.5.11 shipped OpenSSL
>> 1.0.1f (6 Jan 2014) and have been updated to ship OpenSSL 1.0.1g (7 Apr
>> 2014) just a few hours ago.  (The x64 builds are currently being worked
>> on.)  So obviously PHP's OpenSSL extension is affected by the
>> "heartbleed" bug (at least on Windows).
>>
> 
> Does it?  Or does it mean they just want to keep up with the latest 
> release?  And if it does affect PHP, what functions does it affect, and 
> how does it affect them?

I assume PHP does keep up with the latest release because they *are*
affected by the bug e.g. in stream_socket_enable_crypto().


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de