> 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@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
