Federico Di Gregorio <fog@initd.org> writes:
>> Given that as of 7.2, MD5 is the preferred password encryption method
>> and crypt() is deprecated, I'm not inclined to spend a lot of work
>> trying to develop a bulletproof autoconf procedure for making crypt
>> re-entrant. I'm strongly inclined to just document the problem and
>> leave it at that. Comments?
> yes. what about using crypt from DES (reentrant) if postgres is being
> linked with it?
Dunno, how would we detect that? Is it any more portable than crypt_r?
Is it worth the trouble?
> is the MD5 stuff reentrant?
Yes. It's all our own code, so we don't have to rely on the vagaries of
local libraries, either.
regards, tom lane
