Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dAO7v-0005aH-Jn for pgsql-hackers@arkaria.postgresql.org; Mon, 15 May 2017 22:06:03 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dAO7u-0006mm-VF for pgsql-hackers@arkaria.postgresql.org; Mon, 15 May 2017 22:06:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dAO7u-0006mW-AC for pgsql-hackers@postgreSQL.org; Mon, 15 May 2017 22:06:02 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dAO7p-0006zi-Lo for pgsql-hackers@postgreSQL.org; Mon, 15 May 2017 22:06:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v4FM5khb014837; Mon, 15 May 2017 18:05:46 -0400 From: Tom Lane To: Heikki Linnakangas cc: pgsql-hackers@postgreSQL.org Subject: src/test/ssl/t/001_ssltests.pl should not tromp on file permissions MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14835.1494885946.1@sss.pgh.pa.us> Date: Mon, 15 May 2017 18:05:46 -0400 Message-ID: <14836.1494885946@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org I got tripped up while building the 10beta1 tarballs by the fact that src/test/ssl/ssl/client.key had permissions 0600 in my git checkout. After a fair amount of head-scratching, I figured out that this must have been a side-effect of having run the SSL regression tests at some point in the past. I do not like test scripts that scribble on non-transient files, not even (or perhaps especially not) if they're "just" changing the permissions. We could maybe make 001_ssltests.pl save and restore the file's permissions, but I think probably a cleaner answer is to have it make a temporary copy and set the permissions on that. Thoughts? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers