Re: [VOTE] Improved TLS Defaults RFC
On 11 February 2014 13:27, Peter Cowburn <petercowburn@gmail.com> wrote:
> Deprecation of "tls://". Please can I raise a dissenting voice just for
> that particular transport; it currently serves its purpose very well (I can
> has TLS, kthxbye) and asking us to change code to use "ssl://" and add some
> extra context configuration to get the same result seems a little out
> there. This particular change was not discussed in the other thread, in
> point of fact it read to me like "tls://" would not be deprecated [1]. What
> changed? In summary: I'd really rather "tls://" not issue an E_DEPRECATED..
I missed that the first time reading it myself — I'd definitely prefer
tls:// to still exist too, presumably as a direct alias of ssl://. We
might as well let pedantic people like myself who'd rather use the
proper name be happy!
As for the versioned protocols, though: kill them with fire.
> Thanks so much for your time in getting this together. As I started off by
> saying, I'm looking forward to these changing being introduced.
Seconded. I'm really excited about how much better our SSL/TLS
functionality is going to be in PHP 5.6.
Adam
Thread (16 messages)