{"id":1367,"date":"2013-10-17T15:12:51","date_gmt":"2013-10-17T13:12:51","guid":{"rendered":"http:\/\/blog.gocept.com\/?p=1367"},"modified":"2013-10-17T15:19:23","modified_gmt":"2013-10-17T13:19:23","slug":"improving-http-security-at-the-flying-circus","status":"publish","type":"post","link":"https:\/\/blog.gocept.com\/2013\/10\/17\/improving-http-security-at-the-flying-circus\/","title":{"rendered":"Improving HTTP security at the Flying Circus"},"content":{"rendered":"

We now know that the secret services employ extended eavesdropping techniques to scan and analyze nearly all Internet traffic. This worries us since we want to keep our customers’ data confidential. We get a lot of questions about how secure sites hosted at the Flying Circus<\/a> are. As security has many aspects, I would like to focus on one question in this post: How secure is our HTTPS encryption? In other words, is it likely that some third party sitting in the transmission path is able to decrypt traffic between our server and the user’s browser?<\/p>\n

We have checked everything twice to ensure a good level of security with the default configuration of our web server role. Of course no-one can guarantee absolute security, but this is what we do currently:<\/p>\n