From: Mike Gerwitz <mtg@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 32833@debbugs.gnu.org
Subject: bug#32833: IceCat 60 showing sites as "insecure" despite using HTTPS
Date: Tue, 25 Sep 2018 20:30:57 -0400 [thread overview]
Message-ID: <87tvmdcd6m.fsf@gnu.org> (raw)
In-Reply-To: <87a7o5cdv3.fsf@netris.org> (Mark H. Weaver's message of "Tue, 25 Sep 2018 20:16:16 -0400")
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On Tue, Sep 25, 2018 at 20:16:16 -0400, Mark H Weaver wrote:
> Mark H Weaver <mhw@netris.org> writes:
>> To begin, I'm currently building IceCat using the bundled NSPR and NSS,
>> to see if that helps.
>
> Using the bundled NSPR and NSS works around the problem for me. I just
> pushed this change in commit 6d328879378fac95240005233331f596fb5c68ed on
> 'master'. See also the related, immediately preceding commits
> 257e3247910610fe24ae1b86f38e85552d53e48c and
> 94e96f7f68c3b9053fdb5dee5b0ab614163aaa08.
Great!
> I'm keeping this bug report open, since it would be good to find a
> better fix which avoids using the bundled libraries.
I wish I knew enough to suggest a better solution.
It's a little late now, but I just tested the IceCat binary on a Debian
machine and HTTPS works as expected.
Thanks again for your work on this. Maybe I'll let IceCat build
overnight so I can give it a try tomorrow (still on my X200).
--
Mike Gerwitz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2018-09-26 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 4:22 bug#32833: IceCat 60 showing sites as "insecure" despite using HTTPS Mike Gerwitz
2018-09-25 22:01 ` Mark H Weaver
2018-09-26 0:16 ` Mark H Weaver
2018-09-26 0:30 ` Mike Gerwitz [this message]
2018-09-26 4:55 ` Mike Gerwitz
2023-08-29 3:40 ` bug#32833: IceCat 60 certificate validation fails when using system NSS Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvmdcd6m.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=32833@debbugs.gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).