Skip site navigation (1) Skip section navigation (2)

Re: Explanation of pg_authid.rolpassword

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: Explanation of pg_authid.rolpassword
Date: 2010-09-13 01:05:55
Message-ID: AANLkTi=HqNQVRquBFTSgp2D6s89=gkh1thqtzEcsK-sH@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-docs
On Sun, Sep 12, 2010 at 8:57 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Oh, I see.  But I still don't think we really need to provide specific
> examples of what you get when you MD5 particular values... except for
> people who can run the MD5 algorithm in reverse in their head, that
> doesn't seem like it's adding anything.  Second try:
>
> 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.  The md5
> hash will be of the user's password concatenated to their username
> (e.g. if user joe has password xyzzy, PostgreSQL will store the md5
> hash of xyzzyjoe).  If the user has no password, this column will be
> NULL.

This version is fine by me.
Josh

In response to

Responses

pgsql-docs by date

Next:From: Robert HaasDate: 2010-09-13 01:35:01
Subject: Re: Explanation of pg_authid.rolpassword
Previous:From: Robert HaasDate: 2010-09-13 00:57:05
Subject: Re: Explanation of pg_authid.rolpassword

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group