Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id BC14C1EB4C50 for ; Sat, 10 Mar 2012 11:27:15 -0400 (AST) Received: from [2001:4d88:1ffc:463::1] (helo=uvena.de) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S6OCP-0005bJ-Ez for pgsql-admin@postgresql.org; Sat, 10 Mar 2012 15:27:14 +0000 Received: from frank.uvena.de (178-24-54-50-dynip.superkabel.de [178.24.54.50]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uvena.de (Postfix) with ESMTPSA id 04A6E25401D for ; Sat, 10 Mar 2012 15:27:01 +0000 (UTC) Received: from Alpha (localhost [IPv6:::1]) by frank.uvena.de (Postfix) with SMTP id 6BEE115FAC for ; Sat, 10 Mar 2012 16:27:00 +0100 (CET) Date: Sat, 10 Mar 2012 16:26:59 +0100 From: Frank Lanitz To: pgsql-admin@postgresql.org Subject: Re: Disable TRUST authentication mode Message-Id: <20120310162659.c9340f98be1ffb540f277ea4@frank.uvena.de> In-Reply-To: References: <4F5B6EB6.9080507@web.de> <4F5B7033.4010502@web.de> X-Mailer: Sylpheed 3.2.0beta6 (GTK+ 2.24.10; x86_64-pc-linux-gnu) X-Editor: Geany, Emacs X-OS: Debian GNU/Linux Jabber-ID: fralan@jabber.org Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Sat__10_Mar_2012_16_27_00_+0100_p0rtA7CT=I+Hjq2v" X-Host-Lookup-Failed: Reverse DNS lookup failed for 2001:4d88:1ffc:463::1 (failed) X-Pg-Spam-Score: -1.1 (-) X-Archive-Number: 201203/56 X-Sequence-Number: 39244 --Signature=_Sat__10_Mar_2012_16_27_00_+0100_p0rtA7CT=I+Hjq2v Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, 10 Mar 2012 20:51:58 +0530 c k wrote: > 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. Users that are able to change pg_hba.conf are most likely also able to replace any binary at the system. Even you are right that the trust option is a bit dangerous, but its not your root issue.=20 Cheers,=20 Frank --=20 Frank Lanitz --Signature=_Sat__10_Mar_2012_16_27_00_+0100_p0rtA7CT=I+Hjq2v Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJPW3LEAAoJEMTGKa65g3T93RYQAIs4TaGK5pdY7Jbmv9hrfBKC z3VEMlTLSC0kkViZ0sCr36fgTTMHqLN4JycBk3Ei1oiSm/c9wVhqF+60XNMIcLi6 UZkisfZNHlm3AucuTtzTO547V9WZkBciQxcMURLoHLAr//bRYLM7VFYJIL4Ikvly ktrbeWtByPuRnxqD0aCtNBQixxum+BycDBNzMGFIUuGELIAdnUnoyrhVp/8BcECU VNDXyizM6CSszbEoF+Hzc4pn5DMvxyQEfcuK99DLElvJ3lzGr4dH2yTeakiXQQhJ jateV11OIQ8A9kTfsVa7Q2e0O9We7xg3mj7QFRS24L1H/XEz/TcWdl3/7zdng7Kr 5V/Ku/2LOT8G8uXiDU/Z+Ioq+9RrE+g8lHxCXzfQtBaCuj/pHGOjiNIwqJiXL/GW cPmTogcAR/SkkEXTdIQtPW1fK5gNOf6Z5Kq1rnhEFmFhOhJEPcX1gtWyhrv1DCvJ UbEWHNeFnVcJm8NhcZXeFcUUBJA48TcWa5euK6V17u/F+d5GsbLTtjhRpghT1Pgo MQwJesH04ifURnfY4bx7P2wp2w40sX6b+i3qCEUyFQaMI9E7gG7Tln5MukdZK/kG ZOorxjst0KBDP02wtcx9QpV/bzi2mCwCRy8Ebdvf9m1tyio1jGgVXu6/7KPKiTmv FADBWpZd2o0LILwVUNDG =wKKH -----END PGP SIGNATURE----- --Signature=_Sat__10_Mar_2012_16_27_00_+0100_p0rtA7CT=I+Hjq2v--