Re: BUG #15596: Folders created with wrong permissions when installing an extension with a non-default umask

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: a3nm(dot)postgresql(at)a3nm(dot)net
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15596: Folders created with wrong permissions when installing an extension with a non-default umask
Date: 2019-01-17 02:33:41
Message-ID: 3966.1547692421@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> However, the umask of my user is 077, so these "mkdir -p" invocations are
> creating folders that can only be read by root, which is not the intended
> behavior.

So ... don't do that.

> Would it be possible to fix this by redefining MKDIR_P="mkdir -m 0755 -p" in
> pgxs.mk so that the mkdir invocations create the folders with the right
> permissions, in line with the "install" invocations? Thanks!

I think that would be a pretty bad idea, because it would break things
for packagers who have their own ideas about what the directory
permissions ought to be.

You can, of course, enforce your own ideas on the make run with something
like (untested)

make MKDIR_P="mkdir -m 0755 -p" install

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Antoine Amarilli 2019-01-17 10:05:36 Re: BUG #15596: Folders created with wrong permissions when installing an extension with a non-default umask
Previous Message Andrew Gierth 2019-01-17 02:31:56 Re: BUG #15595: matchctx->npatterns is always 1 no matter pattern have 0 or 1 subexpression