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 7FFC93A609F for ; Thu, 13 Jan 2005 21:39:39 +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 24851-07 for ; Thu, 13 Jan 2005 21:39:31 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 620083A61A8 for ; Thu, 13 Jan 2005 21:36:17 +0000 (GMT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 13 Jan 2005 15:36:17 -0600 Subject: Re: Installing PostgreSQL as "postgress" versus "root" From: Scott Marlowe To: "Uwe C. Schroeder" Cc: PostgreSQL Admin In-Reply-To: <200501131313.39366.uwe@oss4u.com> References: <4001DEAF7DF9BD498B58B45051FBEA650207AB73@25exch1.vicorpower.vicr.com> <200501131313.39366.uwe@oss4u.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1105652176.24795.106.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 13 Jan 2005 15:36:16 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.002 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/131 X-Sequence-Number: 15990 On Thu, 2005-01-13 at 15:13, Uwe C. Schroeder wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thursday 13 January 2005 10:52 am, Goulet, Dick wrote: > > Doug, > > > > OK, Assume that the binaries are installed under root, but a > > hacker cracks PostGres, what is to stop him/her from trashing all of the > > database files in the first place? Their not owned by root. Installing > > malware, whether it's actual code or destroying/defacing files causes > > similar if not identical problems. At least their restricted to the > > postgres user. And in my book the executables are of zero value whereas > > the data files, and their contained data, are of infinite value. So > > under your scheme we're protecting the least valuable part of the > > system at the expense of the most valuable. > > So where is the difference? If all executables AND the data is under the > postgres account - an intruder hacking the postgres account would still be > able to destroy your data. > BTW: most commercial software needs root access to be installed - and be it > just to create the user accounts. It doesn't really matter who owns the > executables - if the account owning the files is hacked you're screwed > anyways. When it comes to protecting the data which is the most important > thing after all, replication and backup are your friends. For my larger > customers I'm running replication to two offsite servers (one east-coast, one > texas, just to make sure they're fine when the next earthquake hits) and I do > backups every 8 hours - which are written to a tape and distributed to > another set of offsite servers using rdist. So whatever happens the max they > could ever possibly lose is 8 hours, except there is a full blown nuclear > attack on the whole US - in which case nobody would care about the data > anyways. Like someone pointed out, it might be quite possible to install a trojaned psql executable or some equivalent to harvest passwords, or even a version that when executed by root on accident (i.e. the sysadmin forgets he's logged in as root and runs psql) which then installs a root kit. Also, it might make it easier for a hacker to cover his tracks if he can write to the postgresql binaries.