Format: 1.8 Date: Sat, 25 Feb 2012 11:17:15 +0100 Source: postgresql-8.4 Binary: postgresql-8.4 postgresql-client-8.4 postgresql-server-dev-8.4 postgresql-doc-8.4 postgresql-contrib-8.4 postgresql-plperl-8.4 postgresql-plpython-8.4 postgresql-pltcl-8.4 Architecture: all i386 Version: 8.4.11-1 Distribution: precise Urgency: medium Maintainer: Ubuntu/i386 Build Daemon Changed-By: Martin Pitt Description: postgresql-8.4 - object-relational SQL database, version 8.4 server postgresql-client-8.4 - front-end programs for PostgreSQL 8.4 postgresql-contrib-8.4 - additional facilities for PostgreSQL postgresql-doc-8.4 - documentation for the PostgreSQL database management system postgresql-plperl-8.4 - PL/Perl procedural language for PostgreSQL 8.4 postgresql-plpython-8.4 - PL/Python procedural language for PostgreSQL 8.4 postgresql-pltcl-8.4 - PL/Tcl procedural language for PostgreSQL 8.4 postgresql-server-dev-8.4 - development files for PostgreSQL 8.4 server-side programming Changes: postgresql-8.4 (8.4.11-1) unstable; urgency=medium . * Urgency medium due to security fixes. * New upstream bug fix/security release: - Require execute permission on the trigger function for "CREATE TRIGGER". This missing check could allow another user to execute a trigger function with forged input data, by installing it on a table he owns. This is only of significance for trigger functions marked SECURITY DEFINER, since otherwise trigger functions run as the table owner anyway. (CVE-2012-0866) - Remove arbitrary limitation on length of common name in SSL certificates. Both libpq and the server truncated the common name extracted from an SSL certificate at 32 bytes. Normally this would cause nothing worse than an unexpected verification failure, but there are some rather-implausible scenarios in which it might allow one certificate holder to impersonate another. The victim would have to have a common name exactly 32 bytes long, and the attacker would have to persuade a trusted CA to issue a certificate in which the common name has that string as a prefix. Impersonating a server would also require some additional exploit to redirect client connections. (CVE-2012-0867) - Convert newlines to spaces in names written in pg_dump comments. pg_dump was incautious about sanitizing object names that are emitted within SQL comments in its output script. A name containing a newline would at least render the script syntactically incorrect. Maliciously crafted object names could present a SQL injection risk when the script is reloaded. (CVE-2012-0868) - Fix btree index corruption from insertions concurrent with vacuuming. An index page split caused by an insertion could sometimes cause a concurrently-running "VACUUM" to miss removing index entries that it should remove. After the corresponding table rows are removed, the dangling index entries would cause errors (such as "could not read block N in file ...") or worse, silently wrong query results after unrelated rows are re-inserted at the now-free table locations. This bug has been present since release 8.2, but occurs so infrequently that it was not diagnosed until now. If you have reason to suspect that it has happened in your database, reindexing the affected index will fix things. - Update per-column permissions, not only per-table permissions, when changing table owner. Failure to do this meant that any previously granted column permissions were still shown as having been granted by the old owner. This meant that neither the new owner nor a superuser could revoke the now-untraceable-to-table-owner permissions. - Allow non-existent values for some settings in "ALTER USER/DATABASE SET". Allow default_text_search_config, default_tablespace, and temp_tablespaces to be set to names that are not known. This is because they might be known in another database where the setting is intended to be used, or for the tablespace cases because the tablespace might not be created yet. The same issue was previously recognized for search_path, and these settings now act like that one. - Avoid crashing when we have problems deleting table files post-commit. Dropping a table should lead to deleting the underlying disk files only after the transaction commits. In event of failure then (for instance, because of wrong file permissions) the code is supposed to just emit a warning message and go on, since it's too late to abort the transaction. This logic got broken as of release 8.4, causing such situations to result in a PANIC and an unrestartable database. - Track the OID counter correctly during WAL replay, even when it wraps around. Previously the OID counter would remain stuck at a high value until the system exited replay mode. The practical consequences of that are usually nil, but there are scenarios wherein a standby server that's been promoted to master might take a long time to advance the OID counter to a reasonable value once values are needed. - Fix regular expression back-references with - attached. Rather than enforcing an exact string match, the code would effectively accept any string that satisfies the pattern sub-expression referenced by the back-reference symbol. A similar problem still afflicts back-references that are embedded in a larger quantified expression, rather than being the immediate subject of the quantifier. This will be addressed in a future PostgreSQL release. - Fix recently-introduced memory leak in processing of inet/cidr values. - Fix dangling pointer after "CREATE TABLE AS"/"SELECT INTO" in a SQL-language function. In most cases this only led to an assertion failure in assert-enabled builds, but worse consequences seem possible. - Fix I/O-conversion-related memory leaks in plpgsql. - Improve pg_dump's handling of inherited table columns. pg_dump mishandled situations where a child column has a different default expression than its parent column. If the default is textually identical to the parent's default, but not actually the same (for instance, because of schema search path differences) it would not be recognized as different, so that after dump and restore the child would be allowed to inherit the parent's default. Child columns that are NOT NULL where their parent is not could also be restored subtly incorrectly. - Fix pg_restore's direct-to-database mode for INSERT-style table data. Direct-to-database restores from archive files made with "--inserts" or "--column-inserts" options fail when using pg_restore from a release dated September or December 2011, as a result of an oversight in a fix for another problem. The archive file itself is not at fault, and text-mode output is okay. - Allow AT option in ecpg DEALLOCATE statements. The infrastructure to support this has been there for awhile, but through an oversight there was still an error check rejecting the case. - Fix error in "contrib/intarray"'s int[] & int[] operator. If the smallest integer the two input arrays have in common is 1, and there are smaller values in either array, then 1 would be incorrectly omitted from the result. - Fix error detection in "contrib/pgcrypto"'s encrypt_iv() and decrypt_iv(). These functions failed to report certain types of invalid-input errors, and would instead return random garbage values for incorrect input. - Fix one-byte buffer overrun in "contrib/test_parser". The code would try to read one more byte than it should, which would crash in corner cases. Since "contrib/test_parser" is only example code, this is not a security issue in itself, but bad example code is still bad. - Use __sync_lock_test_and_set() for spinlocks on ARM, if available. This function replaces our previous use of the SWPB instruction, which is deprecated and not available on ARMv6 and later. Reports suggest that the old code doesn't fail in an obvious way on recent ARM boards, but simply doesn't interlock concurrent accesses, leading to bizarre failures in multiprocess operation. - Use "-fexcess-precision=standard" option when building with gcc versions that accept it. This prevents assorted scenarios wherein recent versions of gcc will produce creative results. - Allow use of threaded Python on FreeBSD. Our configure script previously believed that this combination wouldn't work; but FreeBSD fixed the problem, so remove that error check. * Drop 04-armel-tas.patch, applied upstream. Checksums-Sha1: 1747d13dec460a6269e66c29bc492811bac28ba4 1949198 postgresql-doc-8.4_8.4.11-1_all.deb ef80156d8aaa8f8aaf9cbb670a86f4d5e7246299 5425238 postgresql-8.4_8.4.11-1_i386.deb 31dbfbae147bb1668e80e8c846506435be7000f9 1504908 postgresql-client-8.4_8.4.11-1_i386.deb 83d74080f082e616502355c78af9400590772316 631870 postgresql-server-dev-8.4_8.4.11-1_i386.deb 4e2a070ea5ea499a7a0e247ea32a9744dfd6bd99 399872 postgresql-contrib-8.4_8.4.11-1_i386.deb d929cfc9f7867fe52d2b0e9ed0ae7429c36a20e0 38980 postgresql-plperl-8.4_8.4.11-1_i386.deb 5d34be2b6cc3597f47ecfe9e50ee27137f0b7e01 40610 postgresql-plpython-8.4_8.4.11-1_i386.deb 80f19629be84f6795f784d570c3b00b42584e9ee 25952 postgresql-pltcl-8.4_8.4.11-1_i386.deb Checksums-Sha256: e85d3f47ca2922cab6004af52ded5b8cec5430829a989b484d54a30f442d7594 1949198 postgresql-doc-8.4_8.4.11-1_all.deb bd023a1643d2f15dfb9fb1e01c8319996c2ecb5ae3ba9b03ec6738d1cfe1fdf8 5425238 postgresql-8.4_8.4.11-1_i386.deb 5b043a6a1a80ddcd00b0b7d381cca286d8321ae4d103974d75eed11007fb9270 1504908 postgresql-client-8.4_8.4.11-1_i386.deb c4d06c40d744e2273f24c57ce7760b8ca3e3beb24e094ce14c56738dee991c9b 631870 postgresql-server-dev-8.4_8.4.11-1_i386.deb 661fcb0bdc29cffea3014d349a7cbe63843e29d28eab37a0fceef613a50514e5 399872 postgresql-contrib-8.4_8.4.11-1_i386.deb 9d480ca003b7b2b7fd821c176e103b37444fd50268a598417091601e7e1406e0 38980 postgresql-plperl-8.4_8.4.11-1_i386.deb ef2d865715ba8a7a946e91c2df5b0e4aa5ae60f1a691579aceaed01bdb6fa24b 40610 postgresql-plpython-8.4_8.4.11-1_i386.deb f2320bb5bdb7a0db115888ff47f80c441f118dbde8b1300ef40fe006549a5122 25952 postgresql-pltcl-8.4_8.4.11-1_i386.deb Files: f402c310dceb12a92903aff4a2188dd7 1949198 doc optional postgresql-doc-8.4_8.4.11-1_all.deb 9a225ef6e217dd6d9f817ac986a0a575 5425238 database optional postgresql-8.4_8.4.11-1_i386.deb efa44b167f51fb698cfa44333ebb990a 1504908 database optional postgresql-client-8.4_8.4.11-1_i386.deb 6a4f102ea3327314c14670d7afcd3082 631870 libdevel optional postgresql-server-dev-8.4_8.4.11-1_i386.deb 20337a8020f4e066bf0e70823c41cdcf 399872 database optional postgresql-contrib-8.4_8.4.11-1_i386.deb c59b6bfeea8fb565f487783780b100d3 38980 database optional postgresql-plperl-8.4_8.4.11-1_i386.deb b030c0a0b3d5541082ba0f3a881f1209 40610 database optional postgresql-plpython-8.4_8.4.11-1_i386.deb 7573b48b772b9197fc23d699ed9faac3 25952 database optional postgresql-pltcl-8.4_8.4.11-1_i386.deb