Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99030 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55294 invoked from network); 14 May 2017 07:47:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2017 07:47:04 -0000 Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.161 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.161 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.161] ([81.169.146.161:30458] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 71/62-15531-07B08195 for ; Sun, 14 May 2017 03:46:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1494748013; l=2938; s=domk; d=kelunik.com; h=Content-Type:Cc:To:Subject:Date:From:References:In-Reply-To: MIME-Version; bh=dMdifRj+H2fcWiAry6qahT5isPtRWH2IcwAiqsUpCNg=; b=U+FWq/EhXAsa6PFGKXkBBHF6M3DXLU4yIxKb07Q2lLrwFfmUAy9QO4TRrJ3j865Lav IDo7MCPjeDdHSrVGQSVEYu52waj/6MahkcTuXLb0DeH94dchse+y67pf5YzBEQeUi7DH o7M116SOKjWAj0jrpmjcBKcUftoAAhd7rvu54= X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mls2vWuiu+7SLDup6E67mzuoNHBqX83Q== X-RZG-CLASS-ID: mo00 Received: by mail-oi0-f44.google.com with SMTP id b204so103133608oii.1 for ; Sun, 14 May 2017 00:46:53 -0700 (PDT) X-Gm-Message-State: AODbwcBHG8AMYbetwbapo9eEt6WImUM7xc0AvuonhUOgjKbkTj0w6yKX eOr4wo12X1lETMasFoE/jC6XdfME3w== X-Received: by 10.157.48.60 with SMTP id d57mr137705otc.255.1494748012936; Sun, 14 May 2017 00:46:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.156.142 with HTTP; Sun, 14 May 2017 00:46:52 -0700 (PDT) In-Reply-To: <4cba4892-b83a-c4f3-f7f5-aa63cd0b684c@cubiclesoft.com> References: <702de8c0-146e-268f-edf8-d0ea900a87e0@cubiclesoft.com> <4cba4892-b83a-c4f3-f7f5-aa63cd0b684c@cubiclesoft.com> Date: Sun, 14 May 2017 09:46:52 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Thomas Hruska Cc: Anatol Belski , PHP Development Content-Type: multipart/alternative; boundary="001a1134e17a571298054f7724c6" Subject: Re: [PHP-DEV] TLS v1.2 -only- deployments From: me@kelunik.com (Niklas Keller) --001a1134e17a571298054f7724c6 Content-Type: text/plain; charset="UTF-8" > > For NDA reasons, I can't tell you which servers or vendors are involved. > All I know is that I saw a bunch of systems across disparate vendors in a > very short amount of time switching to TLS 1.2 only, which left me confused > and wondering what in the world was going on. Only after someone in a > completely unrelated context forwarded me a message they received from > Authorize.net did I make a PCI DSS connection - all of the systems that > changed are involved with PCI compliance and auditing to various degrees. > Authorize.net recently publicly announced that they are migrating to TLS > 1.2 only and have already switched their sandbox environment over: > > https://community.developer.authorize.net/t5/News-and-Announ > cements/Experiencing-Sandbox-Connection-Issues-TLS-1-2-Is- > Now-Required/td-p/57948 Yes, PayPal also announced these plans quite a while back. https://www.paypal.com/au/webapps/mpp/tls-http-upgrade I'll try to find the PHP 5.6 discussion later today. Regards, Niklas --001a1134e17a571298054f7724c6--