Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id E04AB1EB4C50 for ; Sat, 10 Mar 2012 12:20:45 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S6P2C-0002b8-5a for pgsql-admin@postgresql.org; Sat, 10 Mar 2012 16:20:45 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q2AGKUCO022061; Sat, 10 Mar 2012 11:20:30 -0500 (EST) To: Jan Lentfer cc: c k , pgsql-admin Subject: Re: Disable TRUST authentication mode In-reply-to: <4F5B730E.4020402@web.de> References: <4F5B6EB6.9080507@web.de> <4F5B7033.4010502@web.de> <4F5B730E.4020402@web.de> Comments: In-reply-to Jan Lentfer message dated "Sat, 10 Mar 2012 16:28:14 +0100" Date: Sat, 10 Mar 2012 11:20:30 -0500 Message-ID: <22060.1331396430@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201203/58 X-Sequence-Number: 39246 Jan Lentfer writes: > Am 10.03.2012 16:21, schrieb c k: >> It we can disable the TRUST mode then every user have to login with >> password and every fraud user have to know the password (at least) of >> the user. It is not the case that users from other departments share >> their passwords, but fraud users just bypasses the need to know the >> password. > If they can alter pg_hba.conf they can almost certainly also change/add > users, alter passwords, etc, etc... So from a security perspective it > doesn't buy you much. Somebody who has the ability to rewrite pg_hba.conf could also go in and physically alter the database files -- those are in the same directory tree, with the same ownership and permissions, as pg_hba.conf. If you cannot trust people who have that level of access, you have a problem that software cannot solve for you. You need to rethink who has got access to the machine running the database server, or at least who has got root on it. regards, tom lane