From b7562b7686d38ffe2610631cad2a31ac8e0bb3eb Mon Sep 17 00:00:00 2001 From: Mikaela Suomalainen Date: Mon, 21 Sep 2015 15:48:08 +0300 Subject: [PATCH] znc160ssl: add sha512 & changelog link --- _posts/2015-02-24-znc160-ssl.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/_posts/2015-02-24-znc160-ssl.md b/_posts/2015-02-24-znc160-ssl.md index 3d16ba4..ce4aab3 100644 --- a/_posts/2015-02-24-znc160-ssl.md +++ b/_posts/2015-02-24-znc160-ssl.md @@ -76,6 +76,7 @@ serversslcertfp () { echo "$SSSLCFFN" | openssl x509 -md5 -fingerprint -noout echo "$SSSLCFFN" | openssl x509 -sha1 -fingerprint -noout echo "$SSSLCFFN" | openssl x509 -sha256 -fingerprint -noout + echo "$SSSLCFFN" | openssl x509 -sha512 -fingerprint -noout unset SSSLCFFN } ``` @@ -102,3 +103,8 @@ network. Validating the certificates either by trusted certificates or verifying the fingerprints securely manually protect you from this. If MITM is the case, you shouldn't connect. + +* * * * * + +*As I seem to be updating this page more than I originally thought I should +probably add [this link to changelog here.](https://github.com/Mikaela/mikaela.github.io/commits/master/_posts/2015-02-24-znc160-ssl.md)*