Re: Extra security measures for next week's releases

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: roadrunner6(at)gmx(dot)at
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Extra security measures for next week's releases
Date: 2013-04-03 10:14:32
Message-ID: CABUevEyk=_fZG7yQrFz4n18AQRdFbvYE=V2X=sYihUf=cGVnWA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 3, 2013 at 12:09 PM, <roadrunner6(at)gmx(dot)at> wrote:
> Am 28.03.2013 18:03, schrieb Tom Lane:
>
>> The core committee has decided that one of the security issues due to be
>> fixed next week is sufficiently bad that we need to take extra measures
>> to prevent it from becoming public before packages containing the fix
>> are available. (This is a scenario we've discussed before, but never
>> had to actually implement.)
>>
>
> 8.3 has reached EOL in February 2013, I guess there will be no fix for 8.3,
> right?

That is correct.

Some distributions may backpatch fixes manually, but there will be no
official patch for 8.3.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2013-04-03 13:22:33 Typo in documentation for function to_json
Previous Message roadrunner6 2013-04-03 10:09:44 Re: Extra security measures for next week's releases