From: | Michael Loftis <mloftis(at)wgops(dot)com> |
---|---|
To: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
Cc: | Moritz Sinn <moritz(at)freesources(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: function for creating random id |
Date: | 2002-04-16 18:57:20 |
Message-ID: | 3CBC7410.4070905@wgops.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for the quick reply, I was (literally) sleeping :)
USing MD5 for the user-id is just to try to keep it looking fairly
random, in az a well-built system guessing this hash wouldn't mean
getting access.
Neil Conway wrote:
>On 16 Apr 2002 15:14:09 +0200
>"Moritz Sinn" <moritz(at)freesources(dot)org> wrote:
>
>>Michael Loftis <mloftis(at)wgops(dot)com> writes:
>>
>>>I've gotten intot he habit of using a sequence identifier, and couple
>>>that with the current time then md5 sum that to create unique
>>>uids. Works our fairly well, and is atleast marginally difficult to
>>>guess.
>>>
>>that sounds good. could you send me your function definition? because i
>>don't now how to md5 sum in postgresql.
>>
>
>An implementation of MD5 is part of contrib/pgcrypto.
>
>Cheers,
>
>Neil
>
>P.S. I remember hearing that MD4 has been found to be vulnerable
>already, and that there are some theoretical weaknesses in
>MD5. Does anyone have more info on this? I personally use
>SHA1 anyway...
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Harding | 2002-04-16 18:58:32 | Re: Fw: views |
Previous Message | Stephan Szabo | 2002-04-16 18:53:39 | Re: ON DELETE CASCADE doesn't work |