If you’re using dev-db/postgresql-server, update now.
Today I’ll be masking PostgreSQL 8.3 for removal. If you haven’t already, you should move to a more recent version of PostgreSQL.
The PostgreSQL Global Development Group today released security updates for all active branches of the PostgreSQL database system, including versions 9.1.5, 9.0.9, 8.4.13 and 8.3.20. This update patches security holes associated with libxml2 and libxslt, similar to those affecting other open source projects. All users are urged to update their installations at the first available opportunity.
This security release fixes a vulnerability in the built-in XML functionality, and a vulnerability in the XSLT functionality supplied by the optional XML2 extension. Both vulnerabilities allow reading of arbitrary files by any authenticated database user, and the XSLT vulnerability allows writing files as well. The fixes cause limited backwards compatibility issues. These issues correspond to the following two vulnerabilities:
This release also contains several fixes to version 9.1, and a smaller number of fixes to older versions, including:
- Updates and corrections to time zone data
- Multiple documentation updates and corrections
- Add limit on max_wal_senders
- Fix dependencies generated during ALTER TABLE ADD CONSTRAINT USING INDEX.
- Correct behavior of unicode conversions for PL/Python
- Fix WITH attached to a nested set operation (UNION/INTERSECT/EXCEPT).
- Fix syslogger so that log_truncate_on_rotation works in the first rotation.
- Only allow autovacuum to be auto-canceled by a directly blocked process.
- Improve fsync request queue operation
- Prevent corner-case core dump in rfree().
- Fix Walsender so that it responds correctly to timeouts and deadlocks
- Several PL/Perl fixes for encoding-related issues
- Make selectivity operators use the correct collation
- Prevent unsuitable slaves from being selected for synchronous replication
- Make REASSIGN OWNED work on extensions as well
- Fix race condition with ENUM comparisons
- Make NOTIFY cope with out-of-disk-space
- Fix memory leak in ARRAY subselect queries
- Reduce data loss at replication failover
- Fix behavior of subtransactions with Hot Standby
Users who are relying on the built-in XML functionality to validate external DTDs will need to implement a workaround, as this security patch disables that functionality. Users who are using xslt_process() to fetch documents or stylesheets from external URLs will no longer be able to do so. The PostgreSQL project regrets the need to disable both of these features in order to maintain our security standards. These security issues with XML are substantially similar to issues patched recently by the Webkit (CVE-2011-1774), XMLsec (CVE-2011-1425) and PHP5 (CVE-2012-0057) projects.
As with other minor releases, users are not required to dump and reload their database or use
pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries. Perform post-update steps after the database is restarted.
All supported versions of PostgreSQL are affected. See the release notes for each version for a full list of changes with details of the fixes and steps.
The latest versions are available from Portage now.
So, apparently pgpool-II did a bit of a switcharoo some time ago, which I wasn’t too careful about. But, can you really blame me? pgpool-II’s documentation is among the worst I’ve seen. It’s a good thing they’ve commented their code, or I wouldn’t have been able to do some things cleanly. Continue reading
I have just added a new package to the tree: slimlock. slimlock is a lightweight screen locker that uses the same interface presented by SLiM. Continue reading
pgAdmin 1.14.3 is now available (keyword masked) in Portage. It’s primarily a bug fix release. Continue reading
Multiple potential vulnerabilities have been discovered and fixed in the latest update of PostgreSQL. Upgrade to 9.1.3, 9.0.7, 8.4.11, or 8.3.18 now, don’t wait. The 8.2 branch is EOL and will not have any fixes applied to it. Continue reading
If you do, maybe you want to consider proxy-maintaining it as it now on its way out. Upstream has a much newer version available, and we in the Proxy Maintainers team will be glad to steer you in the right direction when you need the help.
Just send us an email.
PostgreSQL 8.2 has reached the end of its life. Start making your transition now.
From the release announcement (postgresql.org) on December 5, 2011:
This is also the last update for PostgreSQL 8.2, which is now End-Of-Life (EOL). Users of version 8.2 should plan to upgrade their PostgreSQL installations to 8.3 or later within the next couple of months. For more information, see our Release Support Policy. [wiki.postgresql.org]