ubuntu/+source/postgresql-9.1:ubuntu/saucy-devel

Last commit made on 2014-03-21
Get this branch:
git clone -b ubuntu/saucy-devel https://git.launchpad.net/ubuntu/+source/postgresql-9.1
Members of Ubuntu Server Dev import team can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:
ubuntu/saucy-devel
Repository:
lp:ubuntu/+source/postgresql-9.1

Recent commits

8dabc5b... by Martin Pitt on 2014-03-18

Import patches-unapplied version 9.1.13-0ubuntu0.13.10 to ubuntu/saucy-proposed

Imported using git-ubuntu import.

Changelog parent: 9442ba3204a5b496774e77c097a002649004574f

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

9442ba3... by Martin Pitt on 2014-02-20

Import patches-unapplied version 9.1.12-0ubuntu0.13.10 to ubuntu/saucy-security

Imported using git-ubuntu import.

Changelog parent: ec247477cc75140c4ae93bbf66b5baf9e0008704

New changelog entries:
  * New upstream security/bugfix release. (LP: #1282677)
    - Shore up GRANT ... WITH ADMIN OPTION restrictions.
      Granting a role without ADMIN OPTION is supposed to prevent the grantee
      from adding or removing members from the granted role, but this
      restriction was easily bypassed by doing SET ROLE first. The security
      impact is mostly that a role member can revoke the access of others,
      contrary to the wishes of his grantor. Unapproved role member additions
      are a lesser concern, since an uncooperative role member could provide
      most of his rights to others anyway by creating views or SECURITY
      DEFINER functions. (CVE-2014-0060)
    - Prevent privilege escalation via manual calls to PL validator functions.
      The primary role of PL validator functions is to be called implicitly
      during CREATE FUNCTION, but they are also normal SQL functions that a
      user can call explicitly. Calling a validator on a function actually
      written in some other language was not checked for and could be
      exploited for privilege-escalation purposes. The fix involves adding a
      call to a privilege-checking function in each validator function.
      Non-core procedural languages will also need to make this change to
      their own validator functions, if any. (CVE-2014-0061)
    - Avoid multiple name lookups during table and index DDL.
      If the name lookups come to different conclusions due to concurrent
      activity, we might perform some parts of the DDL on a different table
      than other parts. At least in the case of CREATE INDEX, this can be used
      to cause the permissions checks to be performed against a different
      table than the index creation, allowing for a privilege escalation
      attack. (CVE-2014-0062)
    - Prevent buffer overrun with long datetime strings.
      The MAXDATELEN constant was too small for the longest possible value of
      type interval, allowing a buffer overrun in interval_out(). Although the
      datetime input functions were more careful about avoiding buffer
      overrun, the limit was short enough to cause them to reject some valid
      inputs, such as input containing a very long timezone name. The ecpg
      library contained these vulnerabilities along with some of its own.
      (CVE-2014-0063)
    - Prevent buffer overrun due to integer overflow in size calculations.
      Several functions, mostly type input functions, calculated an allocation
      size without checking for overflow. If overflow did occur, a too-small
      buffer would be allocated and then written past. (CVE-2014-0064)
    - Prevent overruns of fixed-size buffers.
      Use strlcpy() and related functions to provide a clear guarantee that
      fixed-size buffers are not overrun. Unlike the preceding items, it is
      unclear whether these cases really represent live issues, since in most
      cases there appear to be previous constraints on the size of the input
      string. Nonetheless it seems prudent to silence all Coverity warnings of
      this type. (CVE-2014-0065)
    - Avoid crashing if crypt() returns NULL.
      There are relatively few scenarios in which crypt() could return NULL,
      but contrib/chkpass would crash if it did. One practical case in which
      this could be an issue is if libc is configured to refuse to execute
      unapproved hashing algorithms (e.g., "FIPS mode"). (CVE-2014-0066)
    - Document risks of make check in the regression testing instructions
      Since the temporary server started by make check uses "trust"
      authentication, another user on the same machine could connect to it as
      database superuser, and then potentially exploit the privileges of the
      operating-system user who started the tests. A future release will
      probably incorporate changes in the testing procedure to prevent this
      risk, but some public discussion is needed first. So for the moment,
      just warn people against using make check when there are untrusted users
      on the same machine. (CVE-2014-0067)
  * The upstream tarballs no longer contain a plain HISTORY file, but point to
    the html documentation. Add 70-history.patch to note the location of these
    files in our changelog.gz file.

ec24747... by Martin Pitt on 2013-12-03

Import patches-unapplied version 9.1.11-0ubuntu0.13.10 to ubuntu/saucy-proposed

Imported using git-ubuntu import.

Changelog parent: 610a7790c1d18752ce5b3990187121fc46256237

New changelog entries:
  * New upstream bug fix release. (LP: #1257211)
    - Fix "VACUUM"'s tests to see whether it can update relfrozenxid.
      In some cases "VACUUM" (either manual or autovacuum) could
      incorrectly advance a table's relfrozenxid value, allowing tuples
      to escape freezing, causing those rows to become invisible once
      2^31 transactions have elapsed. The probability of data loss is
      fairly low since multiple incorrect advancements would need to
      happen before actual loss occurs, but it's not zero. Users
      upgrading from releases 9.0.4 or 8.4.8 or earlier are not affected,
      but all later versions contain the bug.
      The issue can be ameliorated by, after upgrading, vacuuming all
      tables in all databases while having vacuum_freeze_table_age set to
      zero. This will fix any latent corruption but will not be able to
      fix all pre-existing data errors. However, an installation can be
      presumed safe after performing this vacuuming if it has executed
      fewer than 2^31 update transactions in its lifetime (check this
      with SELECT txid_current() < 2^31).
    - Fix initialization of "pg_clog" and "pg_subtrans" during hot
      standby startup.
      This bug can cause data loss on standby servers at the moment they
      start to accept hot-standby queries, by marking committed
      transactions as uncommitted. The likelihood of such corruption is
      small unless, at the time of standby startup, the primary server
      has executed many updating transactions since its last checkpoint.
      Symptoms include missing rows, rows that should have been deleted
      being still visible, and obsolete versions of updated rows being
      still visible alongside their newer versions.
      This bug was introduced in versions 9.3.0, 9.2.5, 9.1.10, and
      9.0.14. Standby servers that have only been running earlier
      releases are not at risk. It's recommended that standby servers
      that have ever run any of the buggy releases be re-cloned from the
      primary (e.g., with a new base backup) after upgrading.
    - See HISTORY/changelog.gz for details about other bug fixes.

610a779... by Martin Pitt on 2013-10-09

Import patches-unapplied version 9.1.10-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 0275bb8c1e5c7cb8268f7ad27b50e1294c9a0d9b

New changelog entries:
  * New upstream bug fix release. See changelog.gz for details.
  * Drop 00git-perl5.18.patch, applied upstream.
  * Add 04-config-update.patch: Refresh config.{guess,sub} to latest version
    for enabling ports, in particular arm64 and the upcoming ppc64el.

0275bb8... by Christoph Berg on 2013-09-10

Import patches-unapplied version 9.1.9-5 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 528e7bb7660a5bff6013a46a6be586e473f7417a

New changelog entries:
  [ Christoph Berg ]
  * Pull 82b0102650cf85268145a46f0ab488bacf6599a1 from upstream head to better
    support VPATH builds of PGXS modules, and make the install targets depend
    on installdirs.
  [ Martin Pitt ]
  * debian/rules: Still build the client-side libraries on Ubuntu.

528e7bb... by Martin Pitt on 2013-08-28

Import patches-unapplied version 9.1.9-4 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 9411748e50f31e93dfd47ff69513bad73d5815fd

New changelog entries:
  * debian/rules: Ignore test suite failures on hurd (unimplemented
    semaphores) and kfreebsd-* (PL tests known to fail).

9411748... by Martin Pitt on 2013-08-27

Import patches-unapplied version 9.1.9-3 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 2ad5aa9aa9c36027ec45048b4b2c093e5afa2901

New changelog entries:
  [ Martin Pitt ]
  * debian/rules: Support multi-arch locations of {tcl,tk}-config.
  * debian/rules: Don't build with kerberos and LDAP support for
    DEB_STAGE=stage1 to aid with bootstrapping.
  * debian/tests/control: Add missing net-tools dependency (for ifconfig).
  * Add 00git-aarch64.patch: Add ARM64 (aarch64) support to s_lock.h.
    Backported from upstream git.
  * debian/rules: Call dh with --parallel.
  * Add 00git-perl5.18.patch: Adjust PL/Perl test cases to also work for Perl
    5.18. Backported from upstream 9.1 stable branch.
  * debian/rules: Don't build client-side libraries unless we have a pgdg
    version, as these are built by -9.3 now.
  [ Christoph Berg ]
  * Pull 6697aa2bc25c83b88d6165340348a31328c35de6 from upstream head to
    better support VPATH builds of PGXS modules.
  * debian/rules, 60-pg_regress_socketdir: Remove the temporary patches from
    pg_regress, and teach pg_regress to support unix socket dirs in --host.
    Use a random port number as well.
  * debian/rules: Use "make check-world" to run the regression tests. Thanks
    to Peter Eisentraut for the suggestion.
  * 61-extra_regress_opts: Add EXTRA_REGRESS_OPTS in Makefile.global(.in) and
    in src/interfaces/ecpg/test/Makefile.

2ad5aa9... by Martin Pitt on 2013-06-19

Import patches-unapplied version 9.1.9-2 to debian/sid

Imported using git-ubuntu import.

Changelog parent: a98d961891b2e713149ed83309eb7f221f1521a9

New changelog entries:
  * debian/copyright: Fix syntax errors.
  * debian/rules: Build with -fno-aggressive-loop-optimizations with gcc 4.8
    to avoid generating bad code due to the broken usage of variable-length
    arrays. This is fixed properly in 9.2, but the patch does not backport
    well. (Closes: #701340)

a98d961... by Martin Pitt on 2013-04-02

Import patches-unapplied version 9.1.9-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 71503c22d6ddcca4f27404a5ad4f5def1f0ca2ea

New changelog entries:
  * Urgency high because of critical remote data destruction vulnerability.
  * New upstream security/bug fix release:
    - Fix insecure parsing of server command-line switches.
      A connection request containing a database name that begins with
      "-" could be crafted to damage or destroy files within the server's
      data directory, even if the request is eventually rejected.
      [CVE-2013-1899] (Closes: #704479)
    - Reset OpenSSL randomness state in each postmaster child process.
      This avoids a scenario wherein random numbers generated by
      "contrib/pgcrypto" functions might be relatively easy for another
      database user to guess. The risk is only significant when the
      postmaster is configured with ssl = on but most connections don't
      use SSL encryption. [CVE-2013-1900]
    - Make REPLICATION privilege checks test current user not
      authenticated user.
      An unprivileged database user could exploit this mistake to call
      pg_start_backup() or pg_stop_backup(), thus possibly interfering
      with creation of routine backups. [CVE-2013-1901]
    - Fix GiST indexes to not use "fuzzy" geometric comparisons when it's
      not appropriate to do so.
      The core geometric types perform comparisons using "fuzzy"
      equality, but gist_box_same must do exact comparisons, else GiST
      indexes using it might become inconsistent. After installing this
      update, users should "REINDEX" any GiST indexes on box, polygon,
      circle, or point columns, since all of these use gist_box_same.
    - Fix erroneous range-union and penalty logic in GiST indexes that
      use "contrib/btree_gist" for variable-width data types, that is
      text, bytea, bit, and numeric columns.
      These errors could result in inconsistent indexes in which some
      keys that are present would not be found by searches, and also in
      useless index bloat. Users are advised to "REINDEX" such indexes
      after installing this update.
    - Fix bugs in GiST page splitting code for multi-column indexes.
      These errors could result in inconsistent indexes in which some
      keys that are present would not be found by searches, and also in
      indexes that are unnecessarily inefficient to search. Users are
      advised to "REINDEX" multi-column GiST indexes after installing
      this update.
    - See HISTORY/changelog.gz for details about the other bug fixes.
  * Bump Standards-Version to 3.9.4 (no changes necessary).

71503c2... by Christoph Berg on 2013-02-05

Import patches-unapplied version 9.1.8-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 7baec73e050dd586f17454e0fb77b39175af602e

New changelog entries:
  [ Martin Pitt ]
  * Add autopkgtest, moved from postgresql-common.
  * debian/rules: Only build the error codes and the plpython subtree for the
    "python3" flavor, to cut down build time.
  * Add missing docbook build dependency. (Closes: #697618)
  [ Christoph Berg ]
  * New upstream version.
    + Prevent execution of enum_recv from SQL
      The function was misdeclared, allowing a simple SQL command to crash the
      server. In principle an attacker might be able to use it to examine the
      contents of server memory. Our thanks to Sumit Soni (via Secunia SVCRP)
      for reporting this issue. (CVE-2013-0255)