X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 46E8E9FB4FD for ; Fri, 22 Sep 2006 15:48:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 40178-02-9 for ; Fri, 22 Sep 2006 15:48:18 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from twmail.ESNCC.COM (static-66-173-159-28.t1.cavtel.net [66.173.159.28]) by postgresql.org (Postfix) with SMTP id 871549FB4F1 for ; Fri, 22 Sep 2006 14:49:11 -0300 (ADT) Received: from spawar2i8uvlb9 ([150.125.117.63]) by twmail.ESNCC.COM with Microsoft SMTPSVC(6.0.3790.1830); Fri, 22 Sep 2006 13:49:06 -0400 From: "Lane Van Ingen" To: Subject: Security Concerns over User 'postgres' Date: Fri, 22 Sep 2006 14:09:23 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0125_01C6DE50.B7F95AC0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 thread-index: AcbecjvKjkiX+JJUTUGvZGkn0yt3JA== Message-ID: X-OriginalArrivalTime: 22 Sep 2006 17:49:07.0192 (UTC) FILETIME=[66ABF780:01C6DE6F] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.186 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200609/247 X-Sequence-Number: 23161 This is a multi-part message in MIME format. ------=_NextPart_000_0125_01C6DE50.B7F95AC0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit We are running on Red Hat Enterprise Linux 4.0, using PostgreSQL 8.1.4 . We created our PostgreSQL instance by compiling it from source, and the instance is working just fine. User postgres runs the service; we do not know what the password is, and we think it got created automatically by the compile / install process. However, my user community is concerned that the password for PostgreSQL (which is MD5 encrypted) could be cracked, and would like to secure it from having access to the shell. I tried attaching /sbin/nologin to the postgres user login information, but that does not work since we use /etc/init.d/postgresql to start and stop the engine. Does anybody have any suggestions on how to properly address these concerns? Lane M. Van Ingen Charleston, SC ------=_NextPart_000_0125_01C6DE50.B7F95AC0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Security Concerns over User 'postgres'

We = are running on Red Hat Enterprise Linux 4.0, using PostgreSQL 8.1.4 = .

We = created our PostgreSQL instance by compiling it from source, and the = instance is working just fine. User postgres runs the service; we do not = know what the password is, and we think it got created automatically by = the compile / install process.

However, my user community is = concerned that the password for PostgreSQL (which is MD5 encrypted) = could be cracked, and would like to secure it = from having access to the shell. I tried attaching /sbin/nologin to the = postgres user login information, but that does not work since we use = /etc/init.d/postgresql to start and stop the engine.

Does = anybody have any suggestions on how = to properly address these concerns?

Lane M. Van = Ingen

Charleston, SC


------=_NextPart_000_0125_01C6DE50.B7F95AC0--