From f61c2c5ff00bf8480d8a636ae221fe46c05f0a19 Mon Sep 17 00:00:00 2001 From: Edoardo Spadolini Date: Thu, 28 Apr 2016 16:10:49 +0300 Subject: [PATCH] 2015-02-24-znc160-ssl.md: Mention `ca_root_nss` for FreeBSD --- _posts/2015-02-24-znc160-ssl.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/_posts/2015-02-24-znc160-ssl.md b/_posts/2015-02-24-znc160-ssl.md index 39caa32..19c951a 100644 --- a/_posts/2015-02-24-znc160-ssl.md +++ b/_posts/2015-02-24-znc160-ssl.md @@ -95,8 +95,9 @@ function like suggested by @DarthGandalf on \#znc.* There are usually four causes for this. Lets use freenode as example network. -1. You don't have `ca-certificates` package installed, so your system - trusts no certificate authority. Install it and try again. +1. You don't have the `ca-certificates` package installed (`ca_root_nss` + on FreeBSD), so your system trusts no certificate authority. Install it + and try again. 2. You are connecting to wrong address. freenode's certificate is valid for \*.freenode.net, but there are CNAMEs pointing there. If you connect to CNAME and the certificate isn't valid for that CNAME, the certificate