Re: SECURITY RELEASES: 7.2.8 - 7.3.10 - 7.4.8 - 8.0.3 - Mailing list pgsql-general

From Douglas McNaught
Subject Re: SECURITY RELEASES: 7.2.8 - 7.3.10 - 7.4.8 - 8.0.3
Date
Msg-id m2hdha83fl.fsf@Douglas-McNaughts-Powerbook.local
Whole thread Raw
In response to Re: SECURITY RELEASES: 7.2.8 - 7.3.10 - 7.4.8 - 8.0.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SECURITY RELEASES: 7.2.8 - 7.3.10 - 7.4.8 - 8.0.3  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Neil Conway <neilc@samurai.com> writes:

>>      http://www.postgresql.org/about/news.315
>
> Also, note that that message was the zero-day-security-problem response
> to the issue, and that we since figured out cleaner responses.  If you
> haven't yet implemented this in your own DBs, I would suggest following
> the procedures given in the final release notes, eg
> http://developer.postgresql.org/docs/postgres/release-7-4-8.html

If we've already done the zero-day fix, is there any value in re-doing
it the "cleaner" way?

-Doug

pgsql-general by date:

Previous
From: Csaba Nagy
Date:
Subject: Fixing a too long column value in a before insert trigger or rule
Next
From: John Dean
Date:
Subject: Rekall for Free