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 20C153A6263 for ; Sat, 29 Jan 2005 17:16:48 +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 98905-10 for ; Sat, 29 Jan 2005 17:16:40 +0000 (GMT) Received: from ncc1701.cistron.net (news.cistron.nl [62.216.30.38]) by svr1.postgresql.org (Postfix) with ESMTP id 498BC3A6065 for ; Sat, 29 Jan 2005 17:16:39 +0000 (GMT) Received: from news by ncc1701.cistron.net with local (Exim 3.36 #1 (Debian)) id 1CuwD8-0004Dq-00 for ; Sat, 29 Jan 2005 18:16:38 +0100 From: list-pgsql-admin@news.cistron.nl ("Miquel van Smoorenburg" ) Reply-To: "Miquel van Smoorenburg" Subject: Re: Installing PostgreSQL as "postgress" versus "root" Debate! Date: Sat, 29 Jan 2005 17:16:38 +0000 (UTC) Organization: Cistron Lines: 22 Message-ID: References: <4001DEAF7DF9BD498B58B45051FBEA650207ABAA@25exch1.vicorpower.vicr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Trace: ncc1701.cistron.net 1107018998 15072 194.109.0.112 (29 Jan 2005 17:16:38 GMT) X-Complaints-To: abuse@cistron.nl X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Originator: mikevs@cistron.nl (mikevs) To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.542 tagged_above=0 required=5 tests=DNS_FROM_RFC_WHOIS, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/292 X-Sequence-Number: 16151 In article <4001DEAF7DF9BD498B58B45051FBEA650207ABAA@25exch1.vicorpower.vicr.com>, Goulet, Dick wrote: > Well, someone I can wholeheartedly agree with. So it really does not >matter who owns the binaries. Once the right account gets hacked your >had. If they hack root your dead, if they hack postgres the database is >had although the server may survive. In either case the state of your >backups is your saving grace or doom. No, it's easier to hack postgres, as the database is running as the postgres user. If you allow something like PgPerl, it's even trivial. The PgPerl script runs as user postgres, and can trojan e.g. the psql executable. The next time someone (perhaps even root ... ) runs psql, they're 0wned. Now it's not that bad an idea to install postgres as a non-root user .. but use a DIFFERENT account to actually start and run postgres. That way your binaries are protected. E.g. install postgres as user 'pgbin', so that all binaries are owned by 'pgbin', then run it as user 'postgres'. Mike.