| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MD5 authentication needs help |
| Date: | 2015-03-04 20:54:09 |
| Message-ID: | 24254.1425502449@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Let me update my list of possible improvements:
> 1) MD5 makes users feel uneasy (though our usage is mostly safe)
> 2) The per-session salt sent to the client is only 32-bits, meaning
> that it is possible to reply an observed MD5 hash in ~16k connection
> attempts.
> 3) Using the user name for the MD5 storage salt allows the MD5 stored
> hash to be used on a different cluster if the user used the same
> password.
> 4) Using the user name for the MD5 storage salt allows the MD5 stored
> hash to be used on the _same_ cluster.
> 5) Using the user name for the MD5 storage salt causes the renaming of
> a user to break the stored password.
What happened to "possession of the contents of pg_authid is sufficient
to log in"? I thought fixing that was one of the objectives here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-03-04 20:56:03 | Re: MD5 authentication needs help |
| Previous Message | Bruce Momjian | 2015-03-04 20:43:27 | Re: MD5 authentication needs help |