Re: [pgadmin-hackers] Client-side password encryption

[Martijn van Oosterhout <kleptog(at)svana(dot)org>]

On Mon, Dec 19, 2005 at 08:51:23AM -0000, Dave Page wrote:
> > Something like
> > 	char *pg_gen_encrypted_passwd(const char *passwd, const 
> > char *user)
> > with malloc'd result (or NULL on failure) seems more future-proof.
> 
> Changing the API is likely to cause fun on Windows for new apps that
> find an old libpq.dll. Perhaps at this point it should become
> libpq82.dll?

Hmm? Libpq already has a version number, I beleive it's upto 4.1 right
now. So if any number is used, it should be that. And secondly, there
have already been new functions added to the API without changing the
library name so why should that happen here?

In windows the trend seems to be to upgrade a library if the one on the
system is too old. If programs are really worried about it, they should
lookup the function dynamically rather than statically...

Have a nice day,
-- 
Martijn van Oosterhout   <kleptog(at)svana(dot)org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

Attachment: pgp5sKJwL9GP3.pgp
Description: PGP signature