ubuntu/+source/postgresql-9.1:debian/wheezy

Last commit made on 2016-06-05
Get this branch:
git clone -b debian/wheezy 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:
debian/wheezy
Repository:
lp:ubuntu/+source/postgresql-9.1

Recent commits

42b7475... by Christoph Berg on 2016-04-02

Import patches-unapplied version 9.1.21-0+deb7u1 to debian/wheezy

Imported using git-ubuntu import.

Changelog parent: 961bfc4b32de52f4131c0aa898744b85da5494a4

New changelog entries:
  * New upstream bugfix release.
  * New upstream version.
    + Fix infinite loops and buffer-overrun problems in regular expressions.
      Very large character ranges in bracket expressions could cause infinite
      loops in some cases, and memory overwrites in other cases.
      (CVE-2016-0773)
    + Fix privilege escalation issue for users of PL/Java. Certain custom
      configuration settings (GUCs) for PL/Java will now be modifiable only by
      the database superuser. (CVE-2016-0766)

961bfc4... by Christoph Berg <email address hidden> on 2015-10-08

Import patches-unapplied version 9.1.19-0+deb7u1 to debian/wheezy

Imported using git-ubuntu import.

Changelog parent: 0a249887c543deeb10b182443a0bc3dc402ceba9

New changelog entries:
  * New upstream version.
    + Fix contrib/pgcrypto to detect and report too-short crypt() salts
      (Josh Kupershmidt)
      Certain invalid salt arguments crashed the server or disclosed a few
      bytes of server memory. We have not ruled out the viability of attacks
      that arrange for presence of confidential information in the disclosed
      bytes, but they seem unlikely. (CVE-2015-5288)

0a24988... by Christoph Berg on 2015-06-11

Import patches-unapplied version 9.1.18-0+deb7u1 to debian/wheezy

Imported using git-ubuntu import.

Changelog parent: a520830327e5aa87ff556d96338b01fc6daecb21

New changelog entries:
  * New upstream version.
    + Fix rare failure to invalidate relation cache init file
  * Remove obsolete .bzr-builddeb/.
  * New upstream version including the fsync fix.
  * Fix fsync-at-startup code to not treat errors as fatal.
    (Abhijit Menon-Sen and Tom Lane, Closes: #786874)
  * New upstream version.
    + Avoid possible crash when client disconnects just before the
      authentication timeout expires (Benkocs Norbert Attila)
      If the timeout interrupt fired partway through the session shutdown
      sequence, SSL-related state would be freed twice, typically causing a
      crash and hence denial of service to other sessions. Experimentation
      shows that an unauthenticated remote attacker could trigger the bug
      somewhat consistently, hence treat as security issue. (CVE-2015-3165)
    + Improve detection of system-call failures (Noah Misch)
      Our replacement implementation of snprintf() failed to check for errors
      reported by the underlying system library calls; the main case that
      might be missed is out-of-memory situations. In the worst case this
      might lead to information exposure, due to our code assuming that a
      buffer had been overwritten when it hadn't been. Also, there were a few
      places in which security-relevant calls of other system library
      functions did not check for failure.
      It remains possible that some calls of the *printf() family of functions
      are vulnerable to information disclosure if an out-of-memory error
      occurs at just the wrong time. We judge the risk to not be large, but
      will continue analysis in this area. (CVE-2015-3166)
    + In contrib/pgcrypto, uniformly report decryption failures as Wrong key
      or corrupt data (Noah Misch)
      Previously, some cases of decryption with an incorrect key could report
      other error message texts. It has been shown that such variance in
      error reports can aid attackers in recovering keys from other systems.
      While it's unknown whether pgcrypto's specific behaviors are likewise
      exploitable, it seems better to avoid the risk by using a
      one-size-fits-all message. (CVE-2015-3167)
  * Repository moved to git, update Vcs headers.
  * New upstream release.
    + Fix buffer overruns in to_char() (CVE-2015-0241)
    + Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243)
    + Fix possible loss of frontend/backend protocol synchronization after an
      error (CVE-2015-0244)
    + Fix information leak via constraint-violation error messages
      (CVE-2014-8161)

a520830... by Christoph Berg on 2014-07-28

Import patches-unapplied version 9.1.14-0+deb7u1 to debian/wheezy

Imported using git-ubuntu import.

Changelog parent: 140c11611889958bacd9f8cf4e9ee6b927bbd1dd

New changelog entries:
  * New upstream release. Noteworthy changes:
    + Secure Unix-domain sockets of temporary postmasters started during make
      check (Noah Misch)
      Any local user able to access the socket file could connect as the
      server's bootstrap superuser, then proceed to execute arbitrary code as
      the operating-system user running the test, as we previously noted in
      CVE-2014-0067. This change defends against that risk by placing the
      server's socket in a temporary, mode 0700 subdirectory of /tmp.
  * Remove debian/pg_regress-in-tmp.patch.

140c116... by Martin Pitt on 2014-03-31

Import patches-unapplied version 9.1.13-0wheezy1 to debian/wheezy

Imported using git-ubuntu import.

Changelog parent: e09f805e8d92eadf72c36a62bac4082b63ac4d3b

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details.
  * New upstream security/bugfix release.
    + Shore up GRANT ... WITH ADMIN OPTION restrictions (Noah Misch)
      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
      (Andres Freund)
      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 (Robert Haas,
      Andres Freund)
      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 (Noah Misch)
      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
      (Noah Misch, Heikki Linnakangas)
      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 (Peter Eisentraut, Jozef Mlich)
      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 (Honza Horak, Bruce Momjian)
      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
      (Noah Misch, Tom Lane)
      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. Note the location of these files in our
    changelog.gz file.

e09f805... by Martin Pitt on 2013-12-05

Import patches-unapplied version 9.1.11-0wheezy1 to debian/wheezy

Imported using git-ubuntu import.

Changelog parent: a98d961891b2e713149ed83309eb7f221f1521a9

New changelog entries:
  * New upstream bug fix release:
    - 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.
  * New upstream bug fix release. See HISTORY/changelog.gz for details.
    (No security or critical issues this time.)

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)

7baec73... by Martin Pitt on 2012-12-03

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

Imported using git-ubuntu import.

Changelog parent: 77a095045fc3cf9ed2788c06f4a0fc0a0f36167d

New changelog entries:
  * New upstream bug fix release. See HISTORY/changelog.gz for details.
  * Add 03-python-includedirs.patch: Detect both python3.3 include locations.
    Thanks Dmitrijs Ledkovs!

77a0950... by Martin Pitt on 2012-09-25

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

Imported using git-ubuntu import.

Changelog parent: b404f5e5ee200f4d50e8472402294e58449b7f32

New changelog entries:
  * Urgency medium because of data loss bug fix.
  * New upstream bug fix release:
    - Fix persistence marking of shared buffers during WAL replay.
      This mistake can result in buffers not being written out during
      checkpoints, resulting in data corruption if the server later
      crashes without ever having written those buffers. Corruption can
      occur on any server following crash recovery, but it is
      significantly more likely to occur on standby slave servers since
      those perform much more WAL replay. There is a low probability of
      corruption of btree and GIN indexes. There is a much higher
      probability of corruption of table "visibility maps". Fortunately,
      visibility maps are non-critical data in 9.1, so the worst
      consequence of such corruption in 9.1 installations is transient
      inefficiency of vacuuming. Table data proper cannot be corrupted by
      this bug.
      While no index corruption due to this bug is known to have occurred
      in the field, as a precautionary measure it is recommended that
      production installations "REINDEX" all btree and GIN indexes at a
      convenient time after upgrading to 9.1.6.
      Also, if you intend to do an in-place upgrade to 9.2.X, before
      doing so it is recommended to perform a "VACUUM" of all tables
      while having vacuum_freeze_table_age set to zero. This will ensure
      that any lingering wrong data in the visibility maps is corrected
      before 9.2.X can depend on it. vacuum_cost_delay can be adjusted to
      reduce the performance impact of vacuuming, while causing it to
      take longer to finish.
    - See HISTORY/changelog.gz for the other bug fixes.
  * debian/rules: Compress all binaries with xz. Thanks Cyril Brulebois!
    (Closes: #688678)