Ubuntu
postgresql-9.3 package

~paelzer/ubuntu/+source/postgresql-9.3:MRE-trusty-9.3.24

  1. Git
  2. lp:~paelzer/ubuntu/+source/postgresql-9.3
  3. MRE-trusty-9.3.24
Last commit made on 2018-08-14
Get this branch:
git clone -b MRE-trusty-9.3.24 https://git.launchpad.net/~paelzer/ubuntu/+source/postgresql-9.3
Only Christian Ehrhardt  can upload to this branch. If you are Christian Ehrhardt  please log in for upload directions.

Branch merges

Branch information

Name:
MRE-trusty-9.3.24
Repository:
lp:~paelzer/ubuntu/+source/postgresql-9.3

Recent commits

a79fe85... by Christian Ehrhardt 

Merge changelog for 9.3.24

Signed-off-by: Christian Ehrhardt <email address hidden>

ae369a0... by Christian Ehrhardt 

Add new pgtypes header and symbol.

Signed-off-by: Christian Ehrhardt <email address hidden>

97cbd9d... by Christian Ehrhardt 

New Upstream release 9.3.24

Signed-off-by: Christian Ehrhardt <email address hidden>

fee03c7... by Christian Ehrhardt 

Import patches-unapplied version 9.3.23-0ubuntu0.14.04 to ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: 58a1ed5698e171e6c1097637d8b892b891c1ead5

New changelog entries:
  * New upstream release (LP: #1769888)
    - A dump/restore is not required for those running 9.3.X.
      However, if the function marking mistakes mentioned in the first
      changelog entry affect you, you will want to take steps to
      correct your database catalogs.
    - Details about changes can be found at
      https://www.postgresql.org/docs/9.3/static/release-9-3-23.html

58a1ed5... by Christian Ehrhardt 

Import patches-unapplied version 9.3.22-0ubuntu0.14.04 to ubuntu/trusty-security

Imported using git-ubuntu import.

Changelog parent: 0cb3b0378c7dfa8445fcf5b458bc94055fde94e2

New changelog entries:
  * New upstream release (LP: #1752271)
    If you run an installation in which not all users are mutually
    trusting, or if you maintain an application or extension that is
    intended for use in arbitrary situations, it is strongly recommended
    that you read the documentation changes described in the first changelog
    entry below, and take suitable steps to ensure that your installation or
    code is secure.
    Also, the changes described in the second changelog entry below may
    cause functions used in index expressions or materialized views to fail
    during auto-analyze, or when reloading from a dump. After upgrading,
    monitor the server logs for such problems, and fix affected functions.
    - Document how to configure installations and applications to guard
      against search-path-dependent trojan-horse attacks from other users
      Using a search_path setting that includes any schemas writable by a
      hostile user enables that user to capture control of queries and then
      run arbitrary SQL code with the permissions of the attacked user. While
      it is possible to write queries that are proof against such hijacking,
      it is notationally tedious, and it's very easy to overlook holes.
      Therefore, we now recommend configurations in which no untrusted schemas
      appear in one's search path.
      (CVE-2018-1058)
    - Avoid use of insecure search_path settings in pg_dump and other client
      programs
      pg_dump, pg_upgrade, vacuumdb and other PostgreSQL-provided applications
      were themselves vulnerable to the type of hijacking described in the
      previous changelog entry; since these applications are commonly run by
      superusers, they present particularly attractive targets. To make them
      secure whether or not the installation as a whole has been secured,
      modify them to include only the pg_catalog schema in their search_path
      settings. Autovacuum worker processes now do the same, as well.
      In cases where user-provided functions are indirectly executed by these
      programs -- for example, user-provided functions in index expressions --
      the tighter search_path may result in errors, which will need to be
      corrected by adjusting those user-provided functions to not assume
      anything about what search path they are invoked under. That has always
      been good practice, but now it will be necessary for correct behavior.
      (CVE-2018-1058)
    - Details about other changes can be found at
      https://www.postgresql.org/docs/9.3/static/release-9-3-22.html

0cb3b03... by Christian Ehrhardt 

Import patches-unapplied version 9.3.21-0ubuntu0.14.04 to ubuntu/trusty-security

Imported using git-ubuntu import.

Changelog parent: 45d8f3c42f37e4b724b1edf88eb8157ee0cb3a49

New changelog entries:
  * New upstream release (LP: #1747676)
    - Ensure that all temporary files made by pg_upgrade are non-world-readable
      (CVE-2018-1053)
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.3/static/release-9-3-21.html

45d8f3c... by Christian Ehrhardt 

Import patches-unapplied version 9.3.20-0ubuntu0.14.04 to ubuntu/trusty-security

Imported using git-ubuntu import.

Changelog parent: 9ea84a3c50833dd7f9170ba66c86d06641bafa99

New changelog entries:
  * New upstream release (LP: #1730661)
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.3/static/release-9-3-20.html

9ea84a3... by Christian Ehrhardt 

Import patches-unapplied version 9.3.19-0ubuntu0.14.04 to ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: ce11244af665606b3244af742206a56824da14aa

New changelog entries:
  * New upstream release (LP: #1713979)
    - fix upgrade regressions of the former security release
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.3/static/release-9-3-19.html

ce11244... by Marc Deslauriers

Import patches-unapplied version 9.3.18-0ubuntu0.14.04.1 to ubuntu/trusty-security

Imported using git-ubuntu import.

Changelog parent: dabd6dd0233021040d28f5bad853872cf7d2dcbb

New changelog entries:
  * SECURITY UPDATE: Update to 9.3.18 to fix security issues
    - Further restrict visibility of pg_user_mappings.umoptions, to protect
      passwords stored as user mapping options (CVE-2017-7547)
    - Disallow empty passwords in all password-based authentication methods
      (CVE-2017-7546)
    - Make lo_put() check for UPDATE privilege on the target large object
      (CVE-2017-7548)

dabd6dd... by Christian Ehrhardt 

Import patches-unapplied version 9.3.17-0ubuntu0.14.04 to ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: 06ec4f1926ea5be074de713810d3d36a2ab4fc62

New changelog entries:
  * New upstream release (LP: #1690730)
    - Restrict visibility of pg_user_mappings.umoptions, to protect passwords
      stored as user mapping options (CVE-2017-7486)
    - Prevent exposure of statistical information via leaky operators
      (CVE-2017-7484)
    - Restore libpq's recognition of the PGREQUIRESSL environment variable
      (CVE-2017-7485)
    - A dump/restore is not required for those running 9.3.X.
    - However, if you use foreign data servers that make use of user passwords
      for authentication, see the first changelog entry.
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.3/static/release-9-3-17.html