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 031923A5077 for ; Thu, 13 Jan 2005 05:09:45 +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 48026-03 for ; Thu, 13 Jan 2005 05:09:40 +0000 (GMT) Received: from mxsf38.cluster1.charter.net (mxsf38.cluster1.charter.net [209.225.28.165]) by svr1.postgresql.org (Postfix) with ESMTP id 1D2533A5F13 for ; Thu, 13 Jan 2005 05:09:39 +0000 (GMT) Received: from mxip08.cluster1.charter.net (mxip08a.cluster1.charter.net [209.225.28.138]) by mxsf38.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id j0D59bU2022406 for ; Thu, 13 Jan 2005 00:09:37 -0500 Received: from 24-159-243-214.jvl.wi.charter.com (HELO shiva) (24.159.243.214) by mxip08.cluster1.charter.net with ESMTP; 13 Jan 2005 00:09:37 -0500 X-Ironport-AV: i="3.88,119,1102309200"; d="scan'208"; a="553848204:sNHT15180912" Received: from quale by shiva with local (Exim 3.36 #1 (Debian)) id 1CoxG0-0003bt-00 for ; Wed, 12 Jan 2005 23:10:52 -0600 To: PgSQL ADMIN Subject: Re: Installing PostgreSQL as "postgress" versus "root" Debate! References: <200501130100.32307.peter_e@gmx.net> <59d991c405011216274c899584@mail.gmail.com> From: Doug Quale Date: 12 Jan 2005 23:10:52 -0600 In-Reply-To: <59d991c405011216274c899584@mail.gmail.com> Message-ID: <87hdll9an7.fsf@charter.net> Lines: 27 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.032 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_POST X-Spam-Level: * X-Archive-Number: 200501/103 X-Sequence-Number: 15962 Christopher Petrilli writes: > 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. A number of years ago some Unices experimented with installing system binaries with owners other than root. Owner 'bin' was one common try. Superficially this sounds good, but experience has shown that it is a bad idea. I don't think anyone does this any longer. Cracking root will compromise standard Unix security no matter who owns the binaries. If system binaries are owned by a user other than root, now you have at least two ids you must protect at all costs. By making things more complex you've just managed to make your job of maintaining security at least twice as hard as it would have been if you had left things alone. Obviously considerations are very different if setuid and setgid programs are involved. Some modern Unices have more advanced security models than the traditional Unix model, so binary ownership may be handled differently in them as well. Mark Twain understood this clearly all the way back in 1894: "Put all your eggs in one basket, and WATCH THAT BASKET."