Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [pgadmin-hackers] Client-side password encryption
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
- Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
- Subject: Re: [pgadmin-hackers] Client-side password encryption
- Date: Mon, 19 Dec 2005 10:00:14 -0500
- Message-id: <29193(dot)1135004414(at)sss(dot)pgh(dot)pa(dot)us>
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes: > Are there any reasons why we shouldn't change the libname with every > release like for UNIX? I can't think of any, but you never know... Surely that cure is far worse than the disease. You'd be trading a might-break risk (app using new function will fail if used with old library) for a guaranteed-to-break risk (*every* app fails if used with *any* library version other than what it was built against). The Unix version of the idea is considerably more flexible than what would happen on Windows. regards, tom lane
- Follow-Ups:
- Re: [pgadmin-hackers] Client-side password encryption
- From: Andreas Pflug
- Re: [pgadmin-hackers] Client-side password encryption
- References:
- Re: [pgadmin-hackers] Client-side password encryption
- From: Dave Page
- Re: [pgadmin-hackers] Client-side password encryption
- From: Martijn van Oosterhout
- Re: [pgadmin-hackers] Client-side password encryption
- Prev by Date: Re: [pgadmin-hackers] Client-side password encryption
- Next by Date: Re: [pgadmin-hackers] Client-side password encryption
- Previous by thread: Re: [pgadmin-hackers] Client-side password encryption
- Next by thread: Re: [pgadmin-hackers] Client-side password encryption
- Indexes: