Skip to contentSkip to conversation

postgresql: security bump to 9.6.7

PATCH Superseded Adam Duskett 2 participants 2 messages Feb 9, 2018 – Feb 10, 2018

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 postgresql: security bump to 9.6.7

from https://www.postgresql.org/about/news/1829/

Fixes:
[1] CVE-2018-1052: Fix the processing of partition keys containing multiple expressions

[2] CVE-2018-1053: Ensure that all temporary files made with "pg_upgrade" are non-world-readable

---
 package/postgresql/postgresql.hash | 4 ++--
 package/postgresql/postgresql.mk   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
package/postgresql/postgresql.hash +2 -2
index e62838911e..4e4bccae13 100644
@@ -1,4 +1,4 @@
-# From https://ftp.postgresql.org/pub/source/v9.6.6/postgresql-9.6.6.tar.bz2.sha256
-sha256 399cdffcb872f785ba67e25d275463d74521566318cfef8fe219050d063c8154  postgresql-9.6.6.tar.bz2
+# From https://ftp.postgresql.org/pub/source/v9.6.7/postgresql-9.6.7.tar.bz2.sha256
+sha256 2ebe3df3c1d1eab78023bdc3ffa55a154aa84300416b075ef996598d78a624c6  postgresql-9.6.7.tar.bz2
 # License file, Locally calculated
 sha256 7dc8de32741ad1b03e21710771b55a1b9d460671d47f28a8840f917e38c66676  COPYRIGHT
package/postgresql/postgresql.mk +1 -1
index 50ce212c1c..86f79c05ee 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-POSTGRESQL_VERSION = 9.6.6
+POSTGRESQL_VERSION = 9.6.7
 POSTGRESQL_SOURCE = postgresql-$(POSTGRESQL_VERSION).tar.bz2
 POSTGRESQL_SITE = http://ftp.postgresql.org/pub/source/v$(POSTGRESQL_VERSION)
 POSTGRESQL_LICENSE = PostgreSQL
Signature · 1 line
2.14.3
#1 lore raw

PATCH 1/1 postgresql: security bump to 9.6.7

Hello,

Quoted 10 lines · Adam Duskett

from https://www.postgresql.org/about/news/1829/

Fixes:
[1] CVE-2018-1052: Fix the processing of partition keys containing multiple expressions

[2] CVE-2018-1053: Ensure that all temporary files made with "pg_upgrade" are non-world-readable

I guess this one is meant for the 2017.02.x branch ?

If so, it would be nice to indicate it in the patch prefix. Same when you send patches intended for the next branch. Use:

git format-patch --subject-prefix="PATCH 2017.02.x"

git format-patch --subject-prefix="PATCH next"

This will make things a lot easier for the people reviewing/applying patches. Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com