The following articles are related to ‘Security’ at CodedMemes.
With the Server 5.1 update providing TLS 1.2 support at last, courtesy of LibreSSL 2.2.6, it’s easy to score A+ on the Qualys SSL Server Test. Here’s a quick run-through of how to get the best performance from the new version.
As of version 5, the Server app still only supports TLS version 1.0 and a handful of suitable ciphers, but even within those constraints, we can improve the situation significantly by shutting off RC4 support and setting a preferred cipher order.
With version 5 of the Server app for OS X, Apache has problems correctly delivering TLS-enabled sites that use aliases, for example wrongly sending the ‘www’ variant of a site to the server’s default site. Here’s how to fix it.
As I described in the previous article in this series, one easy and straightforward approach to handling the transition from SHA-1 to SHA-2 certificates is to install a SHA-1 certificate as the main server certificate and individual SHA-2 certificates for each additional domain hosted on the server.
Coincidentally, I was just finishing up a series on HTTPS on OS X Server when I learned about the Poodle bug. Here’s how to defeat the bug on OS X Mavericks Server.
In this second article of a series on the new HTTPS landscape, I’ll describe one way of supporting both SHA-1 and SHA-2 with OS X Server.
Whoops, Google has decided your site will be at a disadvantage without HTTPS support. Whoops, Google has decided you’ll need to replace that shiny new server certificate you just bought. This is the first in a series of three articles exploring how to adapt.
This site is provided for informational and entertainment purposes only. It is not intended to provide advice of any kind.