From: Roman Mamedov <rm@romanrm.net>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: https://btrfs.wiki.kernel.org having OCSP issues?
Date: Mon, 28 Dec 2015 14:29:43 +0500 [thread overview]
Message-ID: <20151228142943.3ea78db6@natsu> (raw)
In-Reply-To: <pan$d5d71$dbb2da33$97fb9c4d$f6fd4df8@cox.net>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
On Mon, 28 Dec 2015 09:20:09 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
> Firefox is currently giving me OCSP errors for the wiki. Links has no
> problem, presumably because it doesn't validate the cert or ignores OCSP
> timeouts, but lynx is throwing errors as well, so it's not just firefox.
Do you get the same problem with https://www.kernel.org/ ?
Or any other wiki listed at https://wiki.kernel.org/ ?
Can you download http://crl.startssl.com/crt2-crl.crl at your machine?
In general this seems to be a kernel.org webmasters concern, not for Btrfs
developers to do anything about.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-12-28 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 9:20 https://btrfs.wiki.kernel.org having OCSP issues? Duncan
2015-12-28 9:29 ` Roman Mamedov [this message]
2015-12-28 10:34 ` Duncan
2015-12-28 14:03 ` Duncan
2015-12-28 15:39 ` Chris Mason
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=20151228142943.3ea78db6@natsu \
--to=rm@romanrm.net \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).