From: Josh Kupershmidt <schmiddy@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Explanation of pg_authid.rolpassword
Date: Sun, 12 Sep 2010 20:50:29 -0400
Message-ID: <AANLkTimjcoES667kJshbwaiu6DCaaGYFu1e453nrDb+k@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=jyfmjfxnfJHgZb+_WKDmB2CimHzKFOQcPC=Uk@mail.gmail.com>
References: <AANLkTimp=zf0UJvgC356xYAo-OSTV+zXgEsVQZmMnFmH@mail.gmail.com>
<AANLkTi=jyfmjfxnfJHgZb+_WKDmB2CimHzKFOQcPC=Uk@mail.gmail.com>
On Sun, Sep 12, 2010 at 8:36 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Sep 2, 2010 at 11:06 PM, Josh Kupershmidt <schmiddy@gmail.com> wrote:
> This seems a bit long-winded to me. How about just changing the
> column description to something like this:
>
> Either the user's unencrypted password (if the UNENCRYPTED option was
> used when creating the role or if password_encryption is off), or the
> string 'md5' followed by a 32-character hexadecimal md5 hash of the
> user's password. NULL if no password.
I agree my explanation might have been a tad lengthy. But the md5 hash
is of password plus username, not just password. This does seem to
cause confusion; maybe we could leave the example password hashing in
as a footnote on that page?
Josh
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 using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: schmiddy@gmail.com, robertmhaas@gmail.com
Subject: Re: Explanation of pg_authid.rolpassword
In-Reply-To: <AANLkTimjcoES667kJshbwaiu6DCaaGYFu1e453nrDb+k@mail.gmail.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