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 B09859FB3F3 for ; Fri, 22 Sep 2006 17:46:49 -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 90376-02 for ; Fri, 22 Sep 2006 17:46:44 -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 624559FB3EE for ; Fri, 22 Sep 2006 17:46:44 -0300 (ADT) Received: from spawar2i8uvlb9 ([150.125.117.63]) by twmail.ESNCC.COM with Microsoft SMTPSVC(6.0.3790.1830); Fri, 22 Sep 2006 16:46:42 -0400 From: "Lane Van Ingen" To: "'Tom Lane'" Cc: Subject: Re: Security Concerns over User 'postgres' Date: Fri, 22 Sep 2006 17:07:04 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <9540.1158952105@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 thread-index: Acbeenu9pUHch81DSYOIIXnGjwBmuwADxQGg Message-ID: X-OriginalArrivalTime: 22 Sep 2006 20:46:42.0790 (UTC) FILETIME=[35E73060:01C6DE88] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.175 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/250 X-Sequence-Number: 23164 Looked at /etc/shadow, and (in fact) it doesn't have a password, so I was wrong about that. Tried to use the login command to login directly log into postgres, but for some reason could not do that on RHEL 4.0 either. So, like you said, I am not certain that I have a vulnerability here at all, other than su-ing from root. -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Friday, September 22, 2006 3:08 PM To: Lane Van Ingen Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Security Concerns over User 'postgres' "Lane Van Ingen" writes: > 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. Are you sure it even *has* a password? In the default RPM installation, user postgres is created without any password --- the only way to become postgres is to su there from root, and if you've got root you hardly need to crack into postgres. regards, tom lane