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

From Tom Lane
Subject Re: SECURITY RELEASES: 7.2.8 - 7.3.10 - 7.4.8 - 8.0.3
Date
Msg-id 3165.1115817784@sss.pgh.pa.us
Whole thread Raw
In response to Re: SECURITY RELEASES: 7.2.8 - 7.3.10 - 7.4.8 - 8.0.3  (Douglas McNaught <doug@mcnaught.org>)
List pgsql-general
Douglas McNaught <doug@mcnaught.org> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> 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?

Only if you care about allowing unprivileged users to create conversions
(which seems a bit useless to me, but it's in the regression tests...)

            regards, tom lane

pgsql-general by date:

Previous
From: Douglas McNaught
Date:
Subject: Re: Fixing a too long column value in a before insert trigger or rule
Next
From: Thomas F.O'Connell
Date:
Subject: Re: SECURITY RELEASES: 7.2.8 - 7.3.10 - 7.4.8 - 8.0.3