pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kenny Drobnack <kenny@jumpline.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: forcing postgresql 7.3 to use crypt passwords
Date: Wed, 31 Dec 2003 12:31:56 -0500
Message-ID: <1072891915.13899.10.camel@kenny.jlhome.com> (raw)
In-Reply-To: <11189.1072891206@sss.pgh.pa.us>
References: <1072887163.40.4.camel@kenny.jlhome.com>
	<11189.1072891206@sss.pgh.pa.us>

On Wed, 2003-12-31 at 12:20, Tom Lane wrote:
> Kenny Drobnack <kenny@jumpline.com> writes:
> > We currently have multiple databases running different versions of
> > postgresql ranging from version 7.1 to 7.3. When we create users in 7.3
> > databases, it encrypts their passwords with md5, which is not supported
> > in 7.1. Is there some way to force postgresql 7.3 to use the old crypt
> > encryption for passwords when creating users?
> 
> AFAIR the previous approach was not to encrypt passwords at all in
> pg_shadow.  You can still do that with ALTER USER ... UNENCRYPTED PASSWORD
> (also there's a setting to make this the default behavior).
> 
> 			regards, tom lane

Thanks! I got it figured out. I add "password_encryption = false" to
postgresql.conf and did ALTER USER ... PASSWORD on all the users. Then,
found some docs that said the crypt encryption option only encrypts
passwords going across network connections, not in the database. So I've
set that as the authorization method in pg_hba.conf. So we've got
passwords encrypted everywhere except in pg_shadow. It'll due till we
get everything upgraded to 7.3 or preferably 7.4.


-- 
Kenny




view thread (4+ messages)

Message-ID: <1072891915.13899.10.camel@kenny.jlhome.com>
Permalink:  ../1072891915.13899.10.camel@kenny.jlhome.com/
Also on:    postgresql.org/message-id/1072891915.13899.10.camel@kenny.jlhome.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: kenny@jumpline.com, tgl@sss.pgh.pa.us
  Subject: Re: forcing postgresql 7.3 to use crypt passwords
  In-Reply-To: <1072891915.13899.10.camel@kenny.jlhome.com>
  References: <1072887163.40.4.camel@kenny.jlhome.com> <11189.1072891206@sss.pgh.pa.us> <1072891915.13899.10.camel@kenny.jlhome.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