From 69e112fbd1b44a6f9f3380167c12bbe0f76693a1 Mon Sep 17 00:00:00 2001 From: dequis Date: Fri, 6 Jan 2017 11:20:49 -0300 Subject: NEWS: Avoid explicitly mentioning freenode in the pinning examples They have proper certs, so using them as an example is wrong. Particularly worse since they started using letsencrypt recently so every server has a different cert and pubkey. We'll figure out how to link this from the release notes later. --- NEWS | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'NEWS') diff --git a/NEWS b/NEWS index 81c6004c..9604277a 100644 --- a/NEWS +++ b/NEWS @@ -39,16 +39,16 @@ v1.0.0 2017-01-03 The Irssi team values like this: Start by downloading the certificate from a given IRC server: - $ openssl s_client -connect chat.freenode.net:6697 < /dev/null 2>/dev/null | \ - openssl x509 > freenode.cert + $ openssl s_client -connect irc.example.net:6697 < /dev/null 2>/dev/null | \ + openssl x509 > example.cert Find the value for -tls_pinned_cert: - $ openssl x509 -in freenode.cert -fingerprint -sha256 -noout + $ openssl x509 -in example.cert -fingerprint -sha256 -noout Find the value for -tls_pinned_pubkey: - $ openssl x509 -in freenode.cert -pubkey -noout | \ + $ openssl x509 -in example.cert -pubkey -noout | \ openssl pkey -pubin -outform der | \ openssl dgst -sha256 -c | \ tr a-z A-Z -- cgit v1.2.3