<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HTTPS on nagg.eu</title><link>https://nagg.eu/tags/https/</link><description>Recent content in HTTPS on nagg.eu</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 09 Sep 2014 18:02:32 +0000</lastBuildDate><atom:link href="https://nagg.eu/tags/https/index.xml" rel="self" type="application/rss+xml"/><item><title>Get rid of SHA-1 – nginx, TLSv1.2, PFS and SHA-2</title><link>https://nagg.eu/get-rid-of-sha-1-nginx-tlsv1-2-pfs-and-sha-2/</link><pubDate>Tue, 09 Sep 2014 18:02:32 +0000</pubDate><guid>https://nagg.eu/get-rid-of-sha-1-nginx-tlsv1-2-pfs-and-sha-2/</guid><description>&lt;p&gt;Everyone who knows me a little bit knows how much I dislike Google but this time we really should thank them for taking a real step toward a more secure web.&lt;br&gt;
They are finally moving away from SHA-1 to the much more secure SHA-2, more info can be found here: &lt;!-- raw HTML omitted --&gt;&lt;a href="http://googleonlinesecurity.blogspot.it/2014/09/gradually-sunsetting-sha-1.html"&gt;http://googleonlinesecurity.blogspot.it/2014/09/gradually-sunsetting-sha-1.html&lt;/a&gt;&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;
&lt;h3 id="-setup"&gt;.:. Setup&lt;/h3&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;CentOS 6.5 x86_64
nginx/1.6.1
OpenSSL 1.0.1e-fips 11 Feb 2013
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Nginx developers provide an up to date repository (&lt;!-- raw HTML omitted --&gt;&lt;a href="http://wiki.nginx.org/Install"&gt;http://wiki.nginx.org/Install&lt;/a&gt;&lt;!-- raw HTML omitted --&gt;)for CentOS:&lt;/p&gt;</description></item><item><title>nginx and TLS v1.2</title><link>https://nagg.eu/nginx-and-tls-v1-2/</link><pubDate>Sat, 10 Aug 2013 14:03:39 +0000</pubDate><guid>https://nagg.eu/nginx-and-tls-v1-2/</guid><description>&lt;p&gt;Given that SSL and TLS, especially v1.0, suffer from serious security issues (e.g. &lt;!-- raw HTML omitted --&gt;&lt;a href="https://en.wikipedia.org/wiki/Transport_Layer_Security#TLS"&gt;https://en.wikipedia.org/wiki/Transport_Layer_Security#TLS&lt;/a&gt;&lt;!-- raw HTML omitted --&gt;) I thought it would be a good idea to use the latest and more secure version of it: v1.2.&lt;br&gt;
On CentOS 6.4 the openssl version included is quite old and doesn&amp;rsquo;t support TLS v1.1 and 1.2.&lt;br&gt;
So, first of all we have to install the latest version 1.0.1e, it can be done compiling from sources or by adding a third party repository; I chose the latter.&lt;/p&gt;</description></item><item><title>WordPress admin, SSL, Apache + nginx</title><link>https://nagg.eu/wordpress-admin-ssl-apache-nginx/</link><pubDate>Tue, 30 Jul 2013 15:49:37 +0000</pubDate><guid>https://nagg.eu/wordpress-admin-ssl-apache-nginx/</guid><description>&lt;p&gt;Let&amp;rsquo;s say we have a WordPress blog and we would like to encrypt our login pages and the whole back-end of the site.&lt;br&gt;
There are many ways to do it, but since I already have a nginx instance configured as reverse proxy running in front of Apache I&amp;rsquo;ll use it to &lt;code&gt;protect&lt;/code&gt; my admin pages and logins.&lt;br&gt;
In this page I&amp;rsquo;ll not cover Apache&amp;rsquo;s configuration, which, by the way, is trivial to say the least, so please refer to this other post: &lt;!-- raw HTML omitted --&gt;Apache + nginx as reverse proxy&lt;!-- raw HTML omitted --&gt;.&lt;br&gt;
Using the configuration posted in the above&amp;rsquo;s link as starting point, to add SSL encryption to admin pages we should add a couple more bunch of lines of code.&lt;br&gt;
First of all, we must create our own Certificate Authority and issue a SSL certificate.&lt;br&gt;
Another option is buying a certificate, but I don&amp;rsquo;t trust CA (certificate forgery anyone?) and I don&amp;rsquo;t mind having a properly signed certificate for a page I am the only one accessing to.&lt;br&gt;
Follows a brief explanation on how to create a CA and issue a certificate.&lt;/p&gt;</description></item></channel></rss>