Date: Sat, 18 Jun 2016 12:15:35 +0300 From: Kimmo Paasiala <kpaasial@gmail.com> To: Ben Steel <bhs_bsd@precisionforesight.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: new certificate for svn.freebsd.org? Message-ID: <CA%2B7WWSfmgTFhxRaSzdhgfubVGnBUGT5ixW3D=ZAbiei0xz0Mgg@mail.gmail.com> In-Reply-To: <69edafc5-a368-77f6-aee7-81ab3c845e18@precisionforesight.com> References: <69edafc5-a368-77f6-aee7-81ab3c845e18@precisionforesight.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 18, 2016 at 7:40 AM, Ben Steel via freebsd-stable <freebsd-stable@freebsd.org> wrote: > It's not just you, Wolfgang. See bug 210332 at bugs.freebsd.org. > The new certificate is in place on the 4 mirrors that I found (US East, US > West, UK, Russia) but didn't verify cleanly and wasn't in the documentation. > > For me, the fix was in Dimitry's mail, a step I probably missed when > installing security/ca_root_nss: > > sudo ln -s /usr/local/share/certs/ca-root-nss.crt /etc/ssl/cert.pem > > Hope this helps, > > Ben > You might have saved options for security/ca_root_nss which tell the port not to install the symlink. The ETCSYMLINK option has been on by default for quite a long time. Delete the saved options or change them to have the port control the symlink. -Kimmo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B7WWSfmgTFhxRaSzdhgfubVGnBUGT5ixW3D=ZAbiei0xz0Mgg>