Skip site navigation (1) Skip section navigation (2)

Re: libpq not reentrant

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Federico Di Gregorio <fog(at)initd(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: libpq not reentrant
Date: 2002-01-18 15:35:23
Message-ID: 6626.1011368123@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Federico Di Gregorio <fog(at)initd(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: Federico Di GregorioDate: 2002-01-18 15:46:47
Subject: Re: libpq not reentrant
Previous:From: Federico Di GregorioDate: 2002-01-18 15:28:14
Subject: Re: libpq not reentrant

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group