Re: Explanation of pg_authid.rolpassword
От | Josh Kupershmidt |
---|---|
Тема | Re: Explanation of pg_authid.rolpassword |
Дата | |
Msg-id | AANLkTi=HqNQVRquBFTSgp2D6s89=gkh1thqtzEcsK-sH@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Explanation of pg_authid.rolpassword (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Explanation of pg_authid.rolpassword
|
Список | pgsql-docs |
On Sun, Sep 12, 2010 at 8:57 PM, Robert Haas <robertmhaas@gmail.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
В списке pgsql-docs по дате отправления: