Am Donnerstag, 5. Januar 2006 12:40 schrieb Andreas Pflug:
> Ok, we'll use it ASAP. But how to detect if it's available or not? Some
> #define PQENCRYPT_AVAILABLE 1 would be helpful.
Just use
AC_CHECK_FUNCS(PQencryptPassword)
and you will get a definition like that.
---(
Peter Eisentraut wrote:
Am Donnerstag, 5. Januar 2006 12:40 schrieb Andreas Pflug:
Ok, we'll use it ASAP. But how to detect if it's available or not? Some
#define PQENCRYPT_AVAILABLE 1 would be helpful.
Just use
AC_CHECK_FUNCS(PQencryptPassword)
Um, no autoconf in our win32 environment...
Magnus Hagander wrote:
The officially sanctioned function for this is now
PQencryptPassword()
in libpq. Please consider using it when available.
Ok, we'll use it ASAP. But how to detect if it's available or
not? Some #define PQENCRYPT_AVAILABLE 1 would be helpful.
You're going to have
> > The officially sanctioned function for this is now
> PQencryptPassword()
> > in libpq. Please consider using it when available.
>
> Ok, we'll use it ASAP. But how to detect if it's available or
> not? Some #define PQENCRYPT_AVAILABLE 1 would be helpful.
You're going to have to detect this
Peter Eisentraut wrote:
The officially sanctioned function for this is now PQencryptPassword() in
libpq. Please consider using it when available.
Ok, we'll use it ASAP. But how to detect if it's available or not? Some
#define PQENCRYPT_AVAILABLE 1 would be helpful.
Regards,
Andreas
---
The officially sanctioned function for this is now PQencryptPassword() in
libpq. Please consider using it when available.
I wrote:
> Commands like CREATE USER foo PASSWORD 'bar' transmit the password in
> cleartext and possibly save the password in various client or server
> log files. I have j
