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

Re: libpq not reentrant

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Federico Di Gregorio <fog(at)initd(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: libpq not reentrant
Date: 2002-01-18 17:21:06
Message-ID: 200201181721.g0IHL6m22240@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
> So right off the bat, configure is going to have a task guessing
> the correct type of the third argument to crypt_r.  (Who knows what
> it is on other Unixen...)
> 
> 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?

As of 7.2 we are only going to recommend crypt for backward
compatibility with older releases.  I will add a mention in libpq docs
that crypt authentication is not thread-safe.  Even when crypt did work
it wasn't always portable between OS's.  Is that how we want to go?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2002-01-18 17:23:17
Subject: Re: libpq not reentrant
Previous:From: Tom LaneDate: 2002-01-18 16:04:08
Subject: Re: libpq not reentrant

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