X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8B5C23A5EFD for ; Thu, 13 Jan 2005 02:52:47 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 19447-02 for ; Thu, 13 Jan 2005 02:52:36 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 55D7D3A5EF4 for ; Thu, 13 Jan 2005 02:52:39 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0D2qa6T004444; Wed, 12 Jan 2005 21:52:36 -0500 (EST) To: Christopher Petrilli Cc: Peter Eisentraut , "Tomeh, Husam" , PgSQL ADMIN Subject: Re: Installing PostgreSQL as "postgress" versus "root" Debate! In-reply-to: <59d991c405011216274c899584@mail.gmail.com> References: <200501130100.32307.peter_e@gmx.net> <59d991c405011216274c899584@mail.gmail.com> Comments: In-reply-to Christopher Petrilli message dated "Wed, 12 Jan 2005 19:27:51 -0500" Date: Wed, 12 Jan 2005 21:52:36 -0500 Message-ID: <4443.1105584756@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/95 X-Sequence-Number: 15954 Christopher Petrilli writes: > On Thu, 13 Jan 2005 01:00:31 +0100, Peter Eisentraut wrote: >> The current recommendation, which is reflected in the installation >> instructions, is to install the software as root and to use the >> postgres user for the database files. The advice seen elsewhere in >> this thread to use the postgres user also for the software files is >> wrong. > As a security professional, why would the root user need to be > involved in the ownership of PostgreSQL? I see no reason for this, > but perhaps I'm missing something important. The rationale is that the executables should not be owned by the postgres user, so that they can't be corrupted/trojaned if someone manages to break in via the database server. This of course does not require that the executables be owned by root, only by someone other than the daemon account you run the server under. regards, tom lane