linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: https://btrfs.wiki.kernel.org having OCSP issues?
Date: Mon, 28 Dec 2015 10:34:49 +0000 (UTC)	[thread overview]
Message-ID: <pan$59692$556172e2$cc197921$a67a7f3f@cox.net> (raw)
In-Reply-To: 20151228142943.3ea78db6@natsu

Roman Mamedov posted on Mon, 28 Dec 2015 14:29:43 +0500 as excerpted:

> 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/ ?

That one works fine.
 
> Or any other wiki listed at https://wiki.kernel.org/ ?

That one doesn't.  Same sec_error_ocsp_bad_signature error.

> Can you download http://crl.startssl.com/crt2-crl.crl at your machine?

That works fine.  But according to wikipedia (where https is working 
fine, BTW), OCSP was created as an alternative to CRLs.

https://en.wikipedia.org/wiki/Online_Certificate_Status_Protocol

Based on the sequence outlined there and the error firefox is returning, 
seems the OCSP responder is returning responses that don't verify against 
its public key.  So assuming no MitM attack, it'd be the OCSP responder 
that's badly configured, not (directly) wiki.kernel.org or its cert.

> In general this seems to be a kernel.org webmasters concern, not for
> Btrfs developers to do anything about.

Agreed.  But bugzilla.kernel.org is failing with the same error, so I 
can't report the bug there... or even look to see if anyone else has in 
the hour or two since I started seeing issues.  And this is the only vger 
list I follow, so...

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-12-28 10:35 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
2015-12-28 10:34   ` Duncan [this message]
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='pan$59692$556172e2$cc197921$a67a7f3f@cox.net' \
    --to=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).