From: "Branko Grubić" <bitlord0xff@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] net-libs/gnutls-3.7.2 fails to verify some certificates (duplicate server certificate?)
Date: Sat, 27 Nov 2021 15:14:34 +0100 [thread overview]
Message-ID: <b2e429735bd3a3aa2c2274c15f916eebbd0ff88d.camel@gmail.com> (raw)
In-Reply-To: <Y2RJE5VQ.H2UJ77IX.H6WST6KK@7R5XC6AG.AEZMXVPO.A5RMLIR7>
On Tue, 2021-11-23 at 18:14 -0500, Jack wrote:
> OK, here's something.
>
> I changed my stable version of ca-certificates from -cacert to
> cacert,
> and now I get the same failure you do. So - it's due to either
> something in nss-cacert-class1-class3-r2.patch which only gets
> applied
> if that USE flag is set, or to something else only done when that
> USE
> flag is set.
>
> I don't understand it, but it's a place to start - and note the note
> in
> the ebuild:
>
> # When triaging user reports, refer to our wiki for tips:
> #
> https://wiki.gentoo.org/wiki/Certificates#Debugging_certificate_issues
>
Another update, I have masked ~arch ca-certificates:
>app-misc/ca-certificates-20210119.3.66
Downgraded to stable one, and now certificate verification is
successful with gnutls-cli on my test example. Weird since it didn't
fail to verify similar chains with newer app-misc/ca-certificates. I
will file a bug report, but still not sure which component app-mist/ca-
certificates or net-libs/gnutls.
Regards,
Branko
next prev parent reply other threads:[~2021-11-27 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 19:43 [gentoo-user] net-libs/gnutls-3.7.2 fails to verify some certificates (duplicate server certificate?) Branko Grubić
2021-11-23 22:14 ` Jack
2021-11-23 22:26 ` Jack
2021-11-23 22:51 ` Branko Grubić
2021-11-23 23:14 ` Jack
2021-11-26 10:37 ` Branko Grubić
2021-11-27 14:14 ` Branko Grubić [this message]
2021-11-28 5:51 ` [gentoo-user] " Branko Grubić
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=b2e429735bd3a3aa2c2274c15f916eebbd0ff88d.camel@gmail.com \
--to=bitlord0xff@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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