DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	b=UKsSTQlc9v8XlpM6TCMQYqvxGXTq94ctQnDuUXY9ykK+ZqVt+poI5u6efjjTIAJWYE
	BN+t8Ky1mGEVdYo1MJM+RTTFIs2c5EUz2wd5twSdVjImCXbMCFwSLeNuCwSw28MwWOS6
	XSEbLzhJYlpMjqgRnVEdDFix+cp54FFJSe/dQ=
MIME-Version: 1.0
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>
From: Josh Kupershmidt <schmiddy@gmail.com>
Date: Sun, 12 Sep 2010 20:50:29 -0400
Message-ID: <AANLkTimjcoES667kJshbwaiu6DCaaGYFu1e453nrDb+k@mail.gmail.com>
Subject: Re: Explanation of pg_authid.rolpassword
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-docs@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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> wr=
ote:
> This seems a bit long-winded to me. =A0How 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. =A0NULL 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