On 24/04/13 07:36, Frank Ch. Eigler wrote:
Hi -
kenj wrote:
[...] And further I believe it is because our code is using the
sql: prefix
The idea would be drop all the sql: prefixes from our code, and
rely in the NSS environment variable to reactivate it for those
situations where the sysadmin/user prefers it.
That would work, but the default behaviour is different to what we have
released in 3.7.1 (default == only option == sql:) ... my change removes
hard-coded sql: references in the code, and preserves our current
default (sql:) but allows the old style if required.
If we invert the default behaviour we risk messing up anyone who's
already created and installed certificates for secure sockets (although
I expect this may be a small, close to zero-sized, set of people).
when it tries to (again bogusly IMHO) load certificates even though
the client has no interest in secure sockets (and indeed there is no
certificate for pmcd in this installation).
(Yeah, I thought that bug was already understood and fixed or nearly fixed.)
I've not seen any code changes that would suggest this has been fixed,
although I'd love to stand corrected.
|