storing passwords

Started by Brandon Metcalfover 17 years ago3 messagesgeneral
Jump to latest
#1Brandon Metcalf
bmetcalf@nortel.com

We have a number of automated jobs that connect to our pgsql DB and
I'm wondering what others are doing for authentication and securing
passwords. It's easy enough to hardcode a password, but is there
something specific to pgsql, perhaps, that would be a better solution?

Thanks.

--
Brandon

#2Laurent Wandrebeck
l.wandrebeck@gmail.com
In reply to: Brandon Metcalf (#1)
Re: storing passwords

2008/11/5 Brandon Metcalf <bmetcalf@nortel.com>:

We have a number of automated jobs that connect to our pgsql DB and
I'm wondering what others are doing for authentication and securing
passwords. It's easy enough to hardcode a password, but is there
something specific to pgsql, perhaps, that would be a better solution?

http://www.postgresql.org/docs/8.3/interactive/libpq-pgpass.html may
do the trick.

Regards,
Laurent.

#3Steve Atkins
steve@blighty.com
In reply to: Laurent Wandrebeck (#2)
Re: storing passwords

On Nov 5, 2008, at 9:59 AM, Laurent Wandrebeck wrote:

2008/11/5 Brandon Metcalf <bmetcalf@nortel.com>:

We have a number of automated jobs that connect to our pgsql DB and
I'm wondering what others are doing for authentication and securing
passwords. It's easy enough to hardcode a password, but is there
something specific to pgsql, perhaps, that would be a better
solution?

http://www.postgresql.org/docs/8.3/interactive/libpq-pgpass.html may
do the trick.

ident authentication can be a good alternative for scheduled jobs
running
on the same machine as the database too.

Cheers,
Steve