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 E405E3A5FAF for ; Thu, 13 Jan 2005 21:20: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 19386-07 for ; Thu, 13 Jan 2005 21:20:32 +0000 (GMT) Received: from deep.parasun.net (deep.mindlink.net [204.174.16.4]) by svr1.postgresql.org (Postfix) with ESMTP id B14613A5E39 for ; Thu, 13 Jan 2005 21:13:44 +0000 (GMT) Received: from pop.sanbrunocable.com ([65.172.230.120]) by deep.parasun.net with esmtp (Exim 4.43) id 1CpCHl-0006MG-DY for pgsql-admin@postgresql.org; Thu, 13 Jan 2005 13:13:41 -0800 Received: from oss4u.com (cpe-65-172-234-54.sanbrunocable.com [65.172.234.54]) by pop.sanbrunocable.com (8.11.6/8.11.6) with SMTP id j0DLBtY27632 for ; Thu, 13 Jan 2005 13:11:55 -0800 Received: (qmail 18171 invoked from network); 13 Jan 2005 21:08:46 -0000 Received: from tiburon.oss4u.com (192.168.1.4) by gw.oss4u.com (192.168.1.1) with ESMTP; 13 Jan 2005 21:08:46 -0000 From: "Uwe C. Schroeder" Organization: OSS4U, LLC To: "PostgreSQL Admin" Subject: Re: Installing PostgreSQL as "postgress" versus "root" Debate! Date: Thu, 13 Jan 2005 13:13:39 -0800 User-Agent: KMail/1.5.3 References: <4001DEAF7DF9BD498B58B45051FBEA650207AB73@25exch1.vicorpower.vicr.com> In-Reply-To: <4001DEAF7DF9BD498B58B45051FBEA650207AB73@25exch1.vicorpower.vicr.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200501131313.39366.uwe@oss4u.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.102 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/129 X-Sequence-Number: 15988 =2D----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=20 postgres account - an intruder hacking the postgres account would still be= =20 able to destroy your data.=20 BTW: most commercial software needs root access to be installed - and be it= =20 just to create the user accounts. It doesn't really matter who owns the=20 executables - if the account owning the files is hacked you're screwed=20 anyways. When it comes to protecting the data which is the most important=20 thing after all, replication and backup are your friends. For my larger=20 customers I'm running replication to two offsite servers (one east-coast, o= ne=20 texas, just to make sure they're fine when the next earthquake hits) and I = do=20 backups every 8 hours - which are written to a tape and distributed to=20 another set of offsite servers using rdist. So whatever happens the max the= y=20 could ever possibly lose is 8 hours, except there is a full blown nuclear=20 attack on the whole US - in which case nobody would care about the data=20 anyways. > > > Dick Goulet > Senior Oracle DBA > Oracle Certified 8i DBA > -----Original Message----- > From: Doug Quale [mailto:quale1@charter.net] > Sent: Thursday, January 13, 2005 11:56 AM > To: PostgreSQL Admin > Subject: Re: [ADMIN] Installing PostgreSQL as "postgress" versus "root" > Debate! > > "Goulet, Dick" writes: > > to Postgres install as well. I as the DBA should be able to install, > > upgrade, etc the software without access to the root account. Simply > > put the fewer people who know the root password the fewer who can > > destroy the system and the fewer who have to be told when the password > > changes. And the fewer people who know anything, the more secure it > > is. > > This analysis is incomplete. Under this scheme, if someone cracks > your account they can install trojaned or malicious executables owned > by you without cracking root. The flaw is in believing that this > scheme requires an intruder to crack two accounts to defeat your > security. In fact, you have doubled the number of targets but left > the amount of work required of the bad guys to compromise your system > the same (crack one account). > > Put all your eggs in one basket, and WATCH THAT BASKET. > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly =2D --=20 UC =2D -- Open Source Solutions 4U, LLC 2570 Fleetwood Drive Phone: +1 650 872 2425 San Bruno, CA 94066 Cell: +1 650 302 2405 United States =46ax: +1 650 872 2417 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD4DBQFB5uSDjqGXBvRToM4RArMsAJixOHW5IxkLV2Pj838052uQh3oEAJ4oEeUZ 4v+Vdsvv905fMRhA81yQqg=3D=3D =3DP0Py =2D----END PGP SIGNATURE-----