pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Lane Van Ingen <lvaningen@esncc.com>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Security Concerns over User 'postgres'
Date: Fri, 22 Sep 2006 17:07:04 -0400
Message-ID: <TWMAILNzW3l1GM3h3vL00000068@twmail.ESNCC.COM> (raw)
In-Reply-To: <9540.1158952105@sss.pgh.pa.us>

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" <lvaningen@esncc.com> 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




view thread (5+ messages)  latest in thread

Message-ID: <TWMAILNzW3l1GM3h3vL00000068@twmail.ESNCC.COM>
Permalink:  ../TWMAILNzW3l1GM3h3vL00000068@twmail.ESNCC.COM/
Also on:    postgresql.org/message-id/TWMAILNzW3l1GM3h3vL00000068@twmail.ESNCC.COM

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: lvaningen@esncc.com, tgl@sss.pgh.pa.us
  Subject: Re: Security Concerns over User 'postgres'
  In-Reply-To: <TWMAILNzW3l1GM3h3vL00000068@twmail.ESNCC.COM>
  References: <9540.1158952105@sss.pgh.pa.us> <TWMAILNzW3l1GM3h3vL00000068@twmail.ESNCC.COM>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox