Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72478 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31775 invoked from network); 11 Feb 2014 21:33:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Feb 2014 21:33:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.223.180 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.223.180 mail-ie0-f180.google.com Received: from [209.85.223.180] ([209.85.223.180:42674] helo=mail-ie0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/8E-62230-0479AF25 for ; Tue, 11 Feb 2014 16:33:52 -0500 Received: by mail-ie0-f180.google.com with SMTP id u16so179317iet.11 for ; Tue, 11 Feb 2014 13:33:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=y4rEa8TPDUkooMuhGErCT8a0SRyc/AFWAdHMaop02W4=; b=1Qd5w786E76q2H7XphLkUKzRoZ0XJnOReKP2iBf1YoTlr4gzv80ZYymNid4cXwPIEn NzOgMLl+xhMNW7gR9GyUcicl+3e5pyrWo0PLKXdMQQGYOM0Po2U3fIh28WYDFo+erxGf NA8aBB7+rDOoS0g4w8VZkb48M2CVwpv3diGH8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=y4rEa8TPDUkooMuhGErCT8a0SRyc/AFWAdHMaop02W4=; b=hskH8+JYEk0FnBThbFTEhc/3pDtNcN8IFTsq/6uFgf9WOENErYXqPdoEKYxj10fMux zp2586fzLvzf2VPx/7rU7fjO5V6B8ot2miCydq0cwlFx3Hw4bC7l7MKOiO90zOGbr8iW o1F7ats8XvhFx6W79vX0VthKZv7p0EOKjfwZnj9BmyFTbG+AloSCU5uXJ9U52x6y19BU kKXPvNud0UaknXrHO1H9o9t+8aGSwgXX6xWwPKpWMHkWayab9RKO+Zeu+vVuU6rzXTN5 t69dp55uYncVBbQLmKECcKwHqu8PeXetsBBDo7//u+DO2lVuM0hNp96LBy1K6V4RdHmc aszQ== X-Gm-Message-State: ALoCoQksKkw7THVsOKDPjJo+TsVdhUqUTAj+efTUaLjdrtZhXbUaugzEzo4NJGmPrhabe/jpn3pP X-Received: by 10.50.222.99 with SMTP id ql3mr523347igc.42.1392154429504; Tue, 11 Feb 2014 13:33:49 -0800 (PST) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.42.206.208 with HTTP; Tue, 11 Feb 2014 13:33:29 -0800 (PST) In-Reply-To: References: Date: Tue, 11 Feb 2014 13:33:29 -0800 X-Google-Sender-Auth: 1WpcWY_PXuEd4ImHvzdlz_q6gA8 Message-ID: To: Peter Cowburn Cc: Daniel Lowrey , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [VOTE] Improved TLS Defaults RFC From: aharvey@php.net (Adam Harvey) On 11 February 2014 13:27, Peter Cowburn wrote: > Deprecation of "tls://". Please can I raise a dissenting voice just for > that particular transport; it currently serves its purpose very well (I c= an > has TLS, kthxbye) and asking us to change code to use "ssl://" and add so= me > 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]. Wh= at > changed? In summary: I'd really rather "tls://" not issue an E_DEPRECATED= . I missed that the first time reading it myself =E2=80=94 I'd definitely pre= fer 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 b= y > 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