From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> |
Cc: | Jim Mercer <jim(at)reptiles(dot)org>, David Duddleston <david(at)i2a(dot)com>, pgsql-general(at)hub(dot)org |
Subject: | Re: PostgreSQL cleartext passwords |
Date: | 2000-05-24 03:56:55 |
Message-ID: | 5541.959140615@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> writes:
>>> But if someone sniffs the crypted form, won't they be able to reuse it?
>>
>> Not unless they're lucky enough to be challenged with the same random
>> "salt" value that was used in the login transaction they sniffed.
> Well then it's a max of 4096 tries? Assuming a normal crypt size salt.
Right, it's not real strong with standard crypt :-(
However, you must agree that that is the fault of the crypt engine
and not of the protocol. The plan that was being discussed on pghackers
was to replace crypt with an MD5 crypto-hash algorithm and widen the
random salt sufficiently that pure luck wouldn't let an attacker see
the same salt twice. See the archives if you want to pursue this;
I really don't care to repeat the discussion-so-far...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Yeoh | 2000-05-24 04:18:22 | Re: initdb and "exit_nicely"... |
Previous Message | Tom Lane | 2000-05-24 03:51:05 | Re: initdb and "exit_nicely"... |