On 12/17/2013 04:06 PM, Andrea Faulds wrote:
On 17/12/13 11:51, Joe Watkins wrote:
I'm saying that we should, definitely, accept the patch; in this
specific case we can fix the implementation or security issue without
affecting behaviour,
Unfortunately that's not true. To fix the security issue REQUIRES
affecting behaviour. Otherwise it's not fixed.
If the CA file is present with verification enabled the vast majority of requests will execute as they do now, but securely. Most of the time, no evident change. If the CA file is not present change is introduced, lots of it.
Changing the behaviour of the language from an internals perspective does not and should not mean changing the behaviour of code unless that is the intention behind the change, obviously.
Cheers
Joe