Package "postgresql-client-8.4"

Name: postgresql-client-8.4


front-end programs for PostgreSQL 8.4

Latest version: 8.4.22-0ubuntu0.12.04
Release: precise (12.04)
Level: updates
Repository: universe
Head package: postgresql-8.4
Homepage: http://www.postgresql.org/


Download "postgresql-client-8.4"

Other versions of "postgresql-client-8.4" in Precise

Repository Area Version
base universe 8.4.11-1
security universe 8.4.20-0ubuntu0.12.04
PPA: Postgresql 8.4.22-1.pgdg10.4+1
PPA: Postgresql 8.4.22-1.pgdg14.04+1
PPA: Postgresql 8.4.22-1.pgdg12.4+1
PPA: Postgresql 8.4.22-7.pgdg16.04+1
PPA: Postgresql 8.4.22-8.pgdg18.04+1
PPA: Postgresql 8.4.22-9.pgdg20.04+1
PPA: Postgresql 8.4.22-9.pgdg22.04+1


Version: 8.4.22-0ubuntu0.12.04 2014-08-06 21:06:50 UTC

  postgresql-8.4 (8.4.22-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release: (LP: #1348176)
    - Various data integrity and other bug fixes.
    - Secure Unix-domain sockets of temporary postmasters started during make
       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.
    - See release notes for details:
  * Drop pg_regress patch to run tests with socket in /tmp, obsolete with
    above upstream changes and not applicable any more.
 -- Martin Pitt <email address hidden> Tue, 29 Jul 2014 14:47:30 +0200

Source diff to previous version
1348176 New upstream microreleases 9.3.5, 9.1.14, 8.4.22
CVE-2014-0067 The &quot;make check&quot; command for the test suites in PostgreSQL 9.3.3 and ...

Version: 8.4.21-0ubuntu0.12.04 2014-03-31 08:07:09 UTC

  postgresql-8.4 (8.4.21-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)
 -- Martin Pitt <email address hidden> Tue, 18 Mar 2014 10:39:57 +0100

Source diff to previous version

Version: 8.4.20-0ubuntu0.12.04 2014-02-24 14:06:34 UTC

  postgresql-8.4 (8.4.20-0ubuntu0.12.04) precise-security; urgency=medium

  * 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.
    - 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.
 -- Martin Pitt <email address hidden> Thu, 20 Feb 2014 13:15:23 -0800

Source diff to previous version

Version: 8.4.19-0ubuntu0.12.04 2013-12-10 12:07:10 UTC

  postgresql-8.4 (8.4.19-0ubuntu0.12.04) precise-proposed; urgency=low

  * 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 release 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).
    - See HISTORY/changelog.gz for details about bug fixes.
 -- Martin Pitt <email address hidden> Tue, 03 Dec 2013 10:44:58 +0100

Source diff to previous version
1257211 New upstream microreleases 9.1.11, 8.4.19

Version: 8.4.18-0ubuntu12.04 2013-10-24 20:06:56 UTC

  postgresql-8.4 (8.4.18-0ubuntu12.04) precise-proposed; urgency=low

  * New upstream bug fix release (LP: #1237248). No security issues or
    critical issues this time; see HISTORY/changelog.gz for details about bug
 -- Martin Pitt <email address hidden> Wed, 09 Oct 2013 10:12:06 +0200

1237248 New upstream microreleases 9.1.10, 8.4.18

About   -   Send Feedback to @ubuntu_updates