Last-minute updates for release notes.

Security: CVE-2018-1052, CVE-2018-1053

diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index 8be44e33f610378e1347ff7b491d682d2ed1fd2a..6d339db8d333a0d7dbab77463e41edccfdddb378 100644 (file)
--- a/doc/src/sgml/release-9.3.sgml
+++ b/doc/src/sgml/release-9.3.sgml
@@ -33,6 +33,28 @@
 
    
 
+    
+     
+      Ensure that all temporary files made
+      by pg_upgrade are non-world-readable
+      (Tom Lane, Noah Misch)
+     
+
+     
+      pg_upgrade normally restricts its
+      temporary files to be readable and writable only by the calling user.
+      But the temporary file containing pg_dumpall -g
+      output would be group- or world-readable, or even writable, if the
+      user's umask setting allows.  In typical usage on
+      multi-user machines, the umask and/or the working
+      directory's permissions would be tight enough to prevent problems;
+      but there may be people using pg_upgrade
+      in scenarios where this oversight would permit disclosure of database
+      passwords to unfriendly eyes.
+      (CVE-2018-1053)
+     
+    
+
     
      
       Fix vacuuming of tuples that were updated while key-share locked

diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml
index 8817fea473dd55ae28378d785da6964899fbf4f0..da6cf38f70a6b7b751f6c41fca52399ae98ebf94 100644 (file)
--- a/doc/src/sgml/release-9.4.sgml
+++ b/doc/src/sgml/release-9.4.sgml
@@ -33,6 +33,28 @@
 
    
 
+    
+     
+      Ensure that all temporary files made
+      by pg_upgrade are non-world-readable
+      (Tom Lane, Noah Misch)
+     
+
+     
+      pg_upgrade normally restricts its
+      temporary files to be readable and writable only by the calling user.
+      But the temporary file containing pg_dumpall -g
+      output would be group- or world-readable, or even writable, if the
+      user's umask setting allows.  In typical usage on
+      multi-user machines, the umask and/or the working
+      directory's permissions would be tight enough to prevent problems;
+      but there may be people using pg_upgrade
+      in scenarios where this oversight would permit disclosure of database
+      passwords to unfriendly eyes.
+      (CVE-2018-1053)
+     
+    
+
     
      
       Fix vacuuming of tuples that were updated while key-share locked

diff --git a/doc/src/sgml/release-9.5.sgml b/doc/src/sgml/release-9.5.sgml
index aa5fa2c5c9485085cba0f95363b986a82a7dff5e..eb99e4b67e827d42aa5bf677df7b09cf881787e8 100644 (file)
--- a/doc/src/sgml/release-9.5.sgml
+++ b/doc/src/sgml/release-9.5.sgml
@@ -33,6 +33,28 @@
 
    
 
+    
+     
+      Ensure that all temporary files made
+      by pg_upgrade are non-world-readable
+      (Tom Lane, Noah Misch)
+     
+
+     
+      pg_upgrade normally restricts its
+      temporary files to be readable and writable only by the calling user.
+      But the temporary file containing pg_dumpall -g
+      output would be group- or world-readable, or even writable, if the
+      user's umask setting allows.  In typical usage on
+      multi-user machines, the umask and/or the working
+      directory's permissions would be tight enough to prevent problems;
+      but there may be people using pg_upgrade
+      in scenarios where this oversight would permit disclosure of database
+      passwords to unfriendly eyes.
+      (CVE-2018-1053)
+     
+    
+
     
      
       Fix vacuuming of tuples that were updated while key-share locked

diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml
index 6fb02dfaab77aec0ac420454ee6c03b8ecce0a74..dd685c08ad7c33d31fe86a6400e5488d0c8470f8 100644 (file)
--- a/doc/src/sgml/release-9.6.sgml
+++ b/doc/src/sgml/release-9.6.sgml
@@ -39,6 +39,28 @@
 
    
 
+    
+     
+      Ensure that all temporary files made
+      by pg_upgrade are non-world-readable
+      (Tom Lane, Noah Misch)
+     
+
+     
+      pg_upgrade normally restricts its
+      temporary files to be readable and writable only by the calling user.
+      But the temporary file containing pg_dumpall -g
+      output would be group- or world-readable, or even writable, if the
+      user's umask setting allows.  In typical usage on
+      multi-user machines, the umask and/or the working
+      directory's permissions would be tight enough to prevent problems;
+      but there may be people using pg_upgrade
+      in scenarios where this oversight would permit disclosure of database
+      passwords to unfriendly eyes.
+      (CVE-2018-1053)
+     
+    
+
     
      
       Fix vacuuming of tuples that were updated while key-share locked