From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: ca-certificates upgrade for Comodo CA rebrand as Sectigo
Date: Thu, 1 Oct 2020 10:14:03 -0600 [thread overview]
Message-ID: <59fb50cc-6c68-b507-3da1-d66b162bc5cc@SystematicSw.ab.ca> (raw)
In-Reply-To: <announce.20200330134949.93843-1-yselkowitz@cygwin.com>
curl and wget fail or need curl -k --insecure or wget --no-check-certificates
against sites such as https://astro.ukho.gov.uk/ which Chromium allows okay.
I have upgraded ca-certificates locally to current NSS_BUILTINS_LIBRARY_VERSION
2.42 whoch should hopefully handle updates for Comodo CA expiries, transitions,
and rebranding to Sectigo last year.
But curl and wget still have the same issues, so what am I missing?
Is there another global nssdb or cert.db I have to update with certutil, where
is it, and what do I run?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2020-10-01 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 17:49 [ANNOUNCEMENT] ca-certificates 2.40-1 Yaakov Selkowitz
2020-10-01 16:14 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59fb50cc-6c68-b507-3da1-d66b162bc5cc@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).