As a general FYI: cPanel can’t release 2.4.26 until this is patched / fixed. We 
were bitten *hard* by the SCRIPT_URI breakage a while back, and this is going 
to put a blocker on our release.

—
Jacob Perkins
Product Owner
cPanel Inc.

jacob.perk...@cpanel.net <mailto:jacob.perk...@cpanel.net>
Office:  713-529-0800 x 4046
Cell:  713-560-8655

> On Jun 20, 2017, at 12:12 PM, Jim Jagielski <j...@jagunet.com> wrote:
> 
> 
>> On Jun 20, 2017, at 1:03 PM, Jacob Champion <champio...@gmail.com> wrote:
>> 
>> On 06/20/2017 10:00 AM, William A Rowe Jr wrote:
>>> You must presume it is in the wild, and shortening the exposure
>>> by a matter of days isn't significant.
>> 
>> My point is that we should fix it ASAP. Days vs. more days may not be 
>> significant, but days vs. months is definitely significant when it comes to 
>> bug-compatibility and user expectations.
> 
> All this is, IMO, moot until we have a *patch*. Right now there
> is a work-around, which, again IMO, reduces the "need" to release
> something "now"... the only question is whether the patch changes
> the behavior of the 2 current settings or whether it adds a 3rd
> option (the latter is my recommendation).
> 
> And we should update ./t/modules/proxy_fcgi.t and maybe create
> a test which runs if PHP is available.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to