Re: heads up -- subtle change of behavior of new initdb - Mailing list pgsql-hackers

From Greg Stark
Subject Re: heads up -- subtle change of behavior of new initdb
Date
Msg-id 87oevfnni0.fsf@stark.dyndns.tv
Whole thread Raw
In response to Re: heads up -- subtle change of behavior of new initdb  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: heads up -- subtle change of behavior of new initdb
Re: heads up -- subtle change of behavior of new initdb
List pgsql-hackers
> +         if (!chmod(pg_data,0700))

Out of curiosity, what was the rationale for using 0700? I know it was a pain
for me when I had a script to monitor the tmp usage. Surely read access to
privileged users isn't really a problem? I'm thinking more of loosening the
paranoia check elsewhere rather than this default.

Wouldn't at least 0750 be safe? That way putting a user in the postgres group
would grant him access to be able to browse around and read the files in
pg_data.

Actually I should think 02750 would be better so that the group is inherited
by subdirectories.

-- 
greg



pgsql-hackers by date:

Previous
From: Karel Zak
Date:
Subject: Re: XML Docbook
Next
From: Peter Eisentraut
Date:
Subject: Re: heads up -- subtle change of behavior of new initdb