https on {bjørn:johansen}

The future of Certificate Authorities

Mon, 01 Aug 2016 16:38:47 +0000

With the advent of the fully automated and free of cost certificate authorities Let’s Encrypt and StartCom there is no doubt that the future of CAs are changing.

Let’s Encrypt for Nginx

Thu, 31 Mar 2016 20:48:31 +0000

Let’s install an SSL-certificate from Let’s Encrypt for Nginx.

Redirect all HTTP requests to HTTPS with Nginx

Thu, 15 Oct 2015 19:15:43 +0000

All login credentials transferred over plain HTTP can easily be sniffed by an MITM attacker, but is is not enough to encrypt the login forms. If you are visiting plain HTTP pages while logged in, your session can be hijacked, and not even two-factor authentication will protect you. To protect all info sent between your visitors – which includes you – and your web server, we will redirect all requests that are coming over plain HTTP to the HTTPS equivalent.

WordPress behind Big-IP

Mon, 28 Sep 2015 17:09:42 +0000

To be honest, I don’t exactly know too much about Big-IP, but I’ve come across someone who use it. They terminate HTTPS in Big-IP and WordPress runs on plain HTTP on port 80 on the backend nodes. By default, this makes WordPress confused, so you can’t login to the WordPress dashboard.

HTTP Public Key Pinning (HPKP)

Thu, 16 Jul 2015 11:39:19 +0000

Using HTTPS helps preventing someone from snooping your username/password or hijacking your sessions. Using HSTS makes sure the connection stays on HTTPS, even if a MITM tries to redirect you to the plain HTTP version of a web site. But it is easier than you might think for a MITM to use a rogue certificate, making you believe everything is fine. HTTP Public Key Pinning (HPKP) helps the browser check that everything actually is fine.

Optimizing HTTPS on Nginx

Sat, 18 Jan 2014 23:49:30 +0000

Now that you have secured Nginx with HTTPS and enabled SPDY enabled HTTP/2, it’s time to improve both the security and the performance of the server.

Securing Nginx with HTTPS

Thu, 22 Aug 2013 19:53:15 +0000

Adding a certificate and using the HTTPS protocol is a good improvement to the security in the communication between the browser and the server, and should be in place on all sites that have a user login. Contrary to what many (older) guides say, it doesn’t add much load on your server and is fairy easy and cheap to set up right.