-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 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: source all amd64 Version: 8.4.11-1 Distribution: unstable Urgency: medium Maintainer: Martin Pitt <mp...@debian.org> Changed-By: Martin Pitt <mp...@debian.org> 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: f6f1b5ed1ffcbec48528bfab4a61d1745ec61314 2677 postgresql-8.4_8.4.11-1.dsc b12084003937d8ed59287b6db2508e098ac52953 18178451 postgresql-8.4_8.4.11.orig.tar.gz 7a9096dc3d087d3dadcffc138b5656e8772094a5 47454 postgresql-8.4_8.4.11-1.diff.gz 6d1d099737f4479d0264e929c5662be2295dedd7 2187294 postgresql-doc-8.4_8.4.11-1_all.deb d31d902195a07ba692126ee974b6e75c45b12717 5492748 postgresql-8.4_8.4.11-1_amd64.deb 416f439c793c04123be3c32cfe3043f932baa8dc 1538660 postgresql-client-8.4_8.4.11-1_amd64.deb 565f5a00046194f492e7d2201f282583e2e34909 648862 postgresql-server-dev-8.4_8.4.11-1_amd64.deb ffb252378a97b8a5768735fcb9aadaea0c975214 443804 postgresql-contrib-8.4_8.4.11-1_amd64.deb 65f5b74ba8c2bdfbb0aa1c5f3d55f5041a12ef5b 69110 postgresql-plperl-8.4_8.4.11-1_amd64.deb 0bdc46ca147058f82bc91ba62b1c3fab4a12b6a7 70834 postgresql-plpython-8.4_8.4.11-1_amd64.deb 423c8f4fbfe6c9a822abf91e52825f98264545b4 55118 postgresql-pltcl-8.4_8.4.11-1_amd64.deb Checksums-Sha256: 85f997d388564076ca117dd9df8e168fbba56123f6af3cae2c518bf61a31b2ae 2677 postgresql-8.4_8.4.11-1.dsc 5d430fe7b72ad466d477867bad8ee428b25eeefbd161560dc13ac73d77b3541d 18178451 postgresql-8.4_8.4.11.orig.tar.gz 479d4b9915a8464c5966704b3a11d3c39323727eecd48019e0c3d5ac22355f81 47454 postgresql-8.4_8.4.11-1.diff.gz bf43be4916bf7f34ffa7065b4778dd59227412b923ae86b76fa5db8e5a86fa8d 2187294 postgresql-doc-8.4_8.4.11-1_all.deb 7640e800c7f96a5cf5e05326af1d23da8c05e4c61c69fa6c79e7145cca463c17 5492748 postgresql-8.4_8.4.11-1_amd64.deb cfdbb79638e9407e1c7294b16358cb0133dff394821592eae6617301a21abb6c 1538660 postgresql-client-8.4_8.4.11-1_amd64.deb 7df78219431433b2b9b9c55fa7ebb62d998dd0d596b8ecab466e1422c48606d6 648862 postgresql-server-dev-8.4_8.4.11-1_amd64.deb ffd135af512ade1ccb48e80144995333cc1fe844961173aed8bfc75f48a0a107 443804 postgresql-contrib-8.4_8.4.11-1_amd64.deb a3811fd512b4e639681f99530183a20dd33544563e3b1bde987d7564f6fdbe99 69110 postgresql-plperl-8.4_8.4.11-1_amd64.deb 9a6820f02bdd89290536a27efd0e9812b0e8bbf8a9c944b1cca69f1835e36416 70834 postgresql-plpython-8.4_8.4.11-1_amd64.deb 7c2a1cbc254254d286888f486797d81088f0b9db326fd640e23ac3f815efc440 55118 postgresql-pltcl-8.4_8.4.11-1_amd64.deb Files: 098dfface8befc5404eea3879bc67a59 2677 database optional postgresql-8.4_8.4.11-1.dsc 413b8ae9ae6e7f053e2a992e068af63e 18178451 database optional postgresql-8.4_8.4.11.orig.tar.gz f07532ff3a25c2fa56f60c1bfd45f8a9 47454 database optional postgresql-8.4_8.4.11-1.diff.gz 5d227831c59193918224e666d91b7016 2187294 doc optional postgresql-doc-8.4_8.4.11-1_all.deb c699eb4da9ff64eb035ded39d3e824bb 5492748 database optional postgresql-8.4_8.4.11-1_amd64.deb 7934c5a659f9da1ed1872337d1e129db 1538660 database optional postgresql-client-8.4_8.4.11-1_amd64.deb 80fc59d9c65bd247c1daf9341733d527 648862 libdevel optional postgresql-server-dev-8.4_8.4.11-1_amd64.deb e65e99627fdf5e5d576c10cd3ccd29d2 443804 database optional postgresql-contrib-8.4_8.4.11-1_amd64.deb abf3ce5b9262b7fd51d25687ee8f47c0 69110 database optional postgresql-plperl-8.4_8.4.11-1_amd64.deb dbcd2254f76ea3abc6ae564cebcde6f6 70834 database optional postgresql-plpython-8.4_8.4.11-1_amd64.deb dcfe1eeaf21cce5d0cb38e1ee33fa42d 55118 database optional postgresql-pltcl-8.4_8.4.11-1_amd64.deb
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJPSLvEAAoJEPmIJawmtHufY8oP/RLnflLvPu9OvzBKFCpaVD4j PaXOCdrkqiizOFlNCf0NTiXjnXaN9Kef3p6tKip0Awus3KO386YqSPYcHcmEUI53 9miAZlVSGLgpqdgvshiduYhAKfOmqcq0VnGZRB5CoQs35Y+EvUemkAT0b9bjA0sx d/JSgpAbiYdXzXYhyfJNE1LTzJCnP1tCQ70Ui6cNR2ESzaGvBxl1gKNihSMrbxXq f7eqlY+dpQegKBESEuPtk5/02vaGNnLYh4jx6Ix3j9IN50e/lyQOqnv1TMmAy3ny NZ08sLCgI6V+Ws3mUW0572yAavjeWsM7CDbyfbKffSuX8UIfimk9p7Nypl4wxBpT OUhof92o8xDw6mN+ZC1BnvU4UFQccuFylfDeos3EPdSRpDMGfbOycREo0Lbmx8BN oCAj8zSsFuoVMKw1bfd0CrBYWUqGlf+H1KkUHxd1DjpMglU7fdfYbUZCfJkCPyoH /cSeJNQVGXTPJcu85YBLRH7tXCNygcjsPj2EOgnARnkjQjGazTU0dWPXGngtFIHu EthEU4ocIDZV5KYJswgDo2RALhfsAzfHmbFvTivNLFoflALbHwc8mmcQuGZKeMtF Ym1Fe5bNAK8VkUpkrEVcXbC0UGHCq/1SqFMMr3yHfPLTVeLl4SEVEuF2wqD8sLri Ym6XIS3AO5W+25ycLeIv =Gjjz -----END PGP SIGNATURE----- Accepted: postgresql-8.4_8.4.11-1.diff.gz to main/p/postgresql-8.4/postgresql-8.4_8.4.11-1.diff.gz postgresql-8.4_8.4.11-1.dsc to main/p/postgresql-8.4/postgresql-8.4_8.4.11-1.dsc postgresql-8.4_8.4.11-1_amd64.deb to main/p/postgresql-8.4/postgresql-8.4_8.4.11-1_amd64.deb postgresql-8.4_8.4.11.orig.tar.gz to main/p/postgresql-8.4/postgresql-8.4_8.4.11.orig.tar.gz postgresql-client-8.4_8.4.11-1_amd64.deb to main/p/postgresql-8.4/postgresql-client-8.4_8.4.11-1_amd64.deb postgresql-contrib-8.4_8.4.11-1_amd64.deb to main/p/postgresql-8.4/postgresql-contrib-8.4_8.4.11-1_amd64.deb postgresql-doc-8.4_8.4.11-1_all.deb to main/p/postgresql-8.4/postgresql-doc-8.4_8.4.11-1_all.deb postgresql-plperl-8.4_8.4.11-1_amd64.deb to main/p/postgresql-8.4/postgresql-plperl-8.4_8.4.11-1_amd64.deb postgresql-plpython-8.4_8.4.11-1_amd64.deb to main/p/postgresql-8.4/postgresql-plpython-8.4_8.4.11-1_amd64.deb postgresql-pltcl-8.4_8.4.11-1_amd64.deb to main/p/postgresql-8.4/postgresql-pltcl-8.4_8.4.11-1_amd64.deb postgresql-server-dev-8.4_8.4.11-1_amd64.deb to main/p/postgresql-8.4/postgresql-server-dev-8.4_8.4.11-1_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1s20vk-00089j...@franck.debian.org