Autonomous Operator 1.2.0 Public Connectivity
In my previous article I discussed—from a high level—the new Public Connectivity feature in Autonomous Operator 1.2.0. This was intentionally an abstract overview in order to coax the user to learn about the joys of DDNS, TLS and layer 3 Networking.Give a man a fish, and you feed him for a day. Teach a man to fish, and you feed him for a lifetimeHopefully you have all invested the time to learn how to fish! (or at least ready to get your feet wet.) This article gives a practical tutorial on configuration of the Operator in order to be...
Know your SCM_RIGHTS
As TLS 1.3 was ratified earlier this year, I was recollecting how we got started with it here at Cloudflare. We made the decision to be early adopters of TLS 1.3 a little over two years ago. It was a very important decision, and we took it very seriously. It is no secret that Cloudflare uses nginx to handle user traffic. A little less known fact, is that we have several instances of nginx running. I won’t go into detail, but there is one instance whose job is to accept connections on port 443, and proxy them to another instance of nginx that...
How to prepare for the mandatory use of TLS 1.2
In support of our promise to provide best-in-class encryption to our customers, we will be moving to Transport Layer Security (TLS) 1.2 and discontinuing support for TLS versions 1.0 and 1.1. Starting March 29, 2019, we’ll be turning off support for all API requests to Sift Science from servers using those older versions of TLS. Why we’re updating to TLS 1.2 We’re doing this to comply with industry best practices and to provide you with a more secure experience. The TLS protocol is used to encrypt your servers’ communications with...
Service announcement: Removal of support for TLS 1.0
On the 22nd of September 2018, we will begin disabling support for TLS 1.0 in connections to Pusher Channels. Please make sure your clients support at least TLS 1.1. At Pusher, we value security and safety above all else. TLS 1.0 is not as secure as we and many of our customers would like. As time goes on, the standards encourage us to stop supporting less secure versions of TLS. We’ve done this in the past, disabling SSLv3 after the POODLE attack was discovered. Other companies providing cloud services are doing this too. For example,...
