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 DBC0F3A6097 for ; Thu, 13 Jan 2005 23:13:51 +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 45692-05 for ; Thu, 13 Jan 2005 23:13:46 +0000 (GMT) Received: from deep.parasun.net (deep.mindlink.net [204.174.16.4]) by svr1.postgresql.org (Postfix) with ESMTP id 244E23A6378 for ; Thu, 13 Jan 2005 23:13:44 +0000 (GMT) Received: from pop.sanbrunocable.com ([65.172.230.120]) by deep.parasun.net with esmtp (Exim 4.43) id 1CpE9w-00066K-FJ for pgsql-admin@postgresql.org; Thu, 13 Jan 2005 15:13:44 -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 j0DNBw727777 for ; Thu, 13 Jan 2005 15:11:58 -0800 Received: (qmail 19235 invoked from network); 13 Jan 2005 22:42:08 -0000 Received: from tiburon.oss4u.com (192.168.1.4) by gw.oss4u.com (192.168.1.1) with ESMTP; 13 Jan 2005 22:42:08 -0000 From: "Uwe C. Schroeder" Organization: OSS4U, LLC To: Bruce Momjian Subject: Re: Installing PostgreSQL as "postgress" versus "root" Debate! Date: Thu, 13 Jan 2005 14:47:01 -0800 User-Agent: KMail/1.5.3 Cc: PostgreSQL Admin References: <200501132144.j0DLiYv02613@candle.pha.pa.us> In-Reply-To: <200501132144.j0DLiYv02613@candle.pha.pa.us> 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: <200501131447.01510.uwe@oss4u.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.076 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/133 X-Sequence-Number: 15992 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 13 January 2005 01:44 pm, Bruce Momjian wrote: > Uwe C. Schroeder wrote: > [ PGP not available, raw data follows ] > > > -----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.=20 > > > 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. > > To me the difference is that if you your postgres account is hacked and > you installed as root you can delete your /data and start over knowing > the rest of your install is OK. If your binaries are owned by postgres, > you have to reinstall too. > > Of course you might as well reinstall anyway but there is a difference > in knowing the state of the non-/data files. You're right on that one. Although I had a machine hacked a while back (wel= l,=20 I missed updating the flawed ssh version on there). The hacker wasn't reall= y=20 interested in the data, he just wanted another machine to start attacks fro= m=20 =2D - however he managed to install a rootkit. In the case one of my machin= es is=20 hacked I generally scratch the whole machine and reinstall it. There are s= o=20 many ways to mess with the machine that I'm not willing to take the risk=20 missing something the hacker left behind.=20 It would be time to suggest to the linux kernel developers what BSD had for= a=20 long time: The nice flag to lock files even for root access. The only way t= o=20 set or reset that flag on BSD is to shut the machine down in single user=20 mode. If you flag all binaries and configuration files you can be pretty su= re=20 that even with a rootkit the hacker doesn't get far :-) On the other hand=20 it's not very good for machines that have to be up 24/7, so this extra=20 security comes at the trade off on downtime to reconfigure something. 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) iD8DBQFB5vpljqGXBvRToM4RAikmAJ9aTriTSiy94HHexI0pIvPwX3IuuQCfeIlD BQvYK+N9jg+IDHN1ESS8Yr0=3D =3DXrtC =2D----END PGP SIGNATURE-----