pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedSecurity Concerns over User 'postgres'
5+ messages / 4 participants
[nested] [flat]
* Security Concerns over User 'postgres'
@ 2006-09-22 18:09 Lane Van Ingen <lvaningen@esncc.com>
2006-09-22 19:08 ` Re: Security Concerns over User 'postgres' Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Lane Van Ingen @ 2006-09-22 18:09 UTC (permalink / raw)
To: pgsql-admin
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Security Concerns over User 'postgres'
2006-09-22 18:09 Security Concerns over User 'postgres' Lane Van Ingen <lvaningen@esncc.com>
@ 2006-09-22 19:08 ` Tom Lane <tgl@sss.pgh.pa.us>
2006-09-22 19:38 ` Re: Security Concerns over User 'postgres' Marcelo Costa <marcelojscosta@gmail.com>
2006-09-22 21:07 ` Re: Security Concerns over User 'postgres' Lane Van Ingen <lvaningen@esncc.com>
0 siblings, 2 replies; 5+ messages in thread
From: Tom Lane @ 2006-09-22 19:08 UTC (permalink / raw)
To: Lane Van Ingen <lvaningen@esncc.com>; +Cc: pgsql-admin
"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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Security Concerns over User 'postgres'
2006-09-22 18:09 Security Concerns over User 'postgres' Lane Van Ingen <lvaningen@esncc.com>
2006-09-22 19:08 ` Re: Security Concerns over User 'postgres' Tom Lane <tgl@sss.pgh.pa.us>
@ 2006-09-22 19:38 ` Marcelo Costa <marcelojscosta@gmail.com>
1 sibling, 0 replies; 5+ messages in thread
From: Marcelo Costa @ 2006-09-22 19:38 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Lane Van Ingen <lvaningen@esncc.com>; pgsql-admin
Hi,
Only create one user to your aplications and give to her rights to acess
your database
You can change the password of postgresql user
In your linux distro type:
su - postgres
psql -U postgres
in the prompt of postgres type:
# alter user postgres with password 'your new password';
After this your password of user postgres are change.
Create an user to your aplications and give this to all users.
Don´t forget of rights (INSERT,SELECT,UPDATE,DELETE) on your tables to this
user.
[],s
Marcelo Costa
DBA
Executive Secretary of Education from Pará/Amazônia/Brazil
2006/9/22, Tom Lane <tgl@sss.pgh.pa.us>:
>
> "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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
--
Marcelo Costa
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Security Concerns over User 'postgres'
2006-09-22 18:09 Security Concerns over User 'postgres' Lane Van Ingen <lvaningen@esncc.com>
2006-09-22 19:08 ` Re: Security Concerns over User 'postgres' Tom Lane <tgl@sss.pgh.pa.us>
@ 2006-09-22 21:07 ` Lane Van Ingen <lvaningen@esncc.com>
2006-09-22 22:46 ` Re: Security Concerns over User 'postgres' Chris Browne <cbbrowne@acm.org>
1 sibling, 1 reply; 5+ messages in thread
From: Lane Van Ingen @ 2006-09-22 21:07 UTC (permalink / raw)
To: 'Tom Lane' <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Security Concerns over User 'postgres'
2006-09-22 18:09 Security Concerns over User 'postgres' Lane Van Ingen <lvaningen@esncc.com>
2006-09-22 19:08 ` Re: Security Concerns over User 'postgres' Tom Lane <tgl@sss.pgh.pa.us>
2006-09-22 21:07 ` Re: Security Concerns over User 'postgres' Lane Van Ingen <lvaningen@esncc.com>
@ 2006-09-22 22:46 ` Chris Browne <cbbrowne@acm.org>
0 siblings, 0 replies; 5+ messages in thread
From: Chris Browne @ 2006-09-22 22:46 UTC (permalink / raw)
To: pgsql-admin
lvaningen@esncc.com ("Lane Van Ingen") writes:
> 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.
I'm certain; you do NOT have a vulnerability there, if there is no
password in /etc/shadow. (Well, barring stupidity like dramatic
misconfiguration of PAM to accept logins without passwords :-).)
--
(format nil "~S@~S" "cbbrowne" "cbbrowne.com")
http://linuxdatabases.info/info/finances.html
Rules of the Evil Overlord #10. "I will not interrogate my enemies in
the inner sanctum -- a small hotel well outside my borders will work
just as well." <http://www.eviloverlord.com/;
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2006-09-22 22:46 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-09-22 18:09 Security Concerns over User 'postgres' Lane Van Ingen <lvaningen@esncc.com>
2006-09-22 19:08 ` Tom Lane <tgl@sss.pgh.pa.us>
2006-09-22 19:38 ` Marcelo Costa <marcelojscosta@gmail.com>
2006-09-22 21:07 ` Lane Van Ingen <lvaningen@esncc.com>
2006-09-22 22:46 ` Chris Browne <cbbrowne@acm.org>
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