From owner-freebsd-questions@FreeBSD.ORG Fri Sep 12 16:01:29 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CD1B16A4BF for ; Fri, 12 Sep 2003 16:01:29 -0700 (PDT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00E9943FAF for ; Fri, 12 Sep 2003 16:01:28 -0700 (PDT) (envelope-from kirk@strauser.com) Received: from pooh.strauser.com (pooh.honeypot.net [10.0.5.128]) by kanga.honeypot.net (8.12.9/8.12.9) with ESMTP id h8CN1M1T010702; Fri, 12 Sep 2003 18:01:23 -0500 (CDT) (envelope-from kirk@strauser.com) To: alexander v p References: From: Kirk Strauser Date: Fri, 12 Sep 2003 18:01:19 -0500 In-Reply-To: (alexander v. p.'s message of "Fri, 12 Sep 2003 18:36:43 -0400 (EDT)") Message-ID: <87ad99bohs.fsf@strauser.com> Lines: 24 X-Mailer: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" cc: "Andrew L. Gould" cc: freebsd-questions@freebsd.org Subject: Re: Trying to secure PostgreSQL X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 23:01:29 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable At 2003-09-12T22:36:43Z, alexander v p writes: > look in /usr/local/pgsql/data/pg_hba.conf=20 > by default is: > > local all all trust > host all all 127.0.0.1 255.255.255.255 trust > > what you have to do is to change trust into password or md5 > hope that helps > alex > p.s. restart postgres after you change the conf file. But when I do that, I'm prompted to enter the password for 'pgsql' whenever I start the service. That's pretty inconvenient when it's part of the boot process; the system would be effectively hung until I accessed the box, entered the password, and let the init sequence finish. I'd read of people coming up with a mechanism to pipe a password from some (hopefully) secure file on the system into the password prompt. Is that really the best way to handle this? =2D-=20 Kirk Strauser --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQA/YlBC5sRg+Y0CpvERAqQkAJ4xChZkwEz3qZV2Ak7PnPglVxjhxgCcCT/f hR+4+DmJWm1Mm1ubeZX9tIw= =w3k1 -----END PGP SIGNATURE----- --=-=-=--