Re: [HACKERS] Extra security measures for next week's releases

2013-04-03 Thread roadrunner6

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?





--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


Re: [HACKERS] Extra security measures for next week's releases

2013-04-03 Thread Magnus Hagander
On Wed, Apr 3, 2013 at 12:09 PM,  roadrunn...@gmx.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/


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers