Re: Securing "make check" (CVE-2014-0067)
Noah Misch <noah@leadboat.com>
From: Noah Misch <noah@leadboat.com>
To: pgsql-hackers@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>
Date: 2014-03-23T23:04:20Z
Lists: pgsql-hackers
Attachments
- makecheck-socket-secure-v1.patch (text/plain) patch v1
On Thu, Mar 06, 2014 at 11:52:22PM -0500, Noah Misch wrote: > On Thu, Mar 06, 2014 at 12:44:34PM -0500, Tom Lane wrote: > > I'm inclined to suggest that we should put the socket under $CWD by > > default, but provide some way for the user to override that choice. > > If they want to put it in /tmp, it's on their head as to how secure > > that is. On most modern platforms it'd be fine. > > I am skeptical about the value of protecting systems with non-sticky /tmp, but > long $CWD isn't of great importance, either. I'm fine with your suggestion. > Though the $CWD or one of its parents could be world-writable, that would > typically mean an attacker could just replace the test cases directly. Here's the patch. The temporary data directory makes for a convenient socket directory; initdb already gives it mode 0700, and we have existing arrangements to purge it when finished. One can override the socket directory by defining PG_REGRESS_SOCK_DIR in the environment. nm -- Noah Misch EnterpriseDB http://www.enterprisedb.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Have config_sspi_auth() permit IPv6 localhost connections.
- 8d9cb0bc4834 9.5.0 cited
-
Lock down regression testing temporary clusters on Windows.
- f6dc6dd5ba54 9.5.0 cited
-
Use a separate temporary directory for the Unix-domain socket
- f545d233ebce 9.5.0 cited
-
Secure Unix-domain sockets of "make check" temporary clusters.
- be76a6d39e28 9.5.0 cited