unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: 22408@debbugs.gnu.org
Subject: bug#22408: wget rejects Let's Encrypt certs, although Icecat accepts them
Date: Wed, 20 Jan 2016 00:03:49 -0500	[thread overview]
Message-ID: <20160120050349.GA5962@jasmine> (raw)
In-Reply-To: <87twm9tzk2.fsf@netris.org>

On Tue, Jan 19, 2016 at 09:27:09AM -0500, Mark H Weaver wrote:
> On recent GuixSD, IceCat accepts the Let's Encrypt certificate from
> https://git.dthompson.us/, but 'wget' rejects it:
> 
>   mhw@jojen:~$ wget https://git.dthompson.us/presentations.git/blob/HEAD:/guix-blu-2016-01-20.pdf
>   --2016-01-19 09:23:23--  https://git.dthompson.us/presentations.git/blob/HEAD:/guix-blu-2016-01-20.pdf
>   Resolving git.dthompson.us (git.dthompson.us)... 23.92.20.238
>   Connecting to git.dthompson.us (git.dthompson.us)|23.92.20.238|:443... connected.
>   ERROR: The certificate of ‘git.dthompson.us’ is not trusted.
>   ERROR: The certificate of ‘git.dthompson.us’ hasn't got a known issuer.

I don't think this issue is specific to our packaging. On up-to-date
Debian testing, I have the same result from Debian's wget.

I don't know how good the ssllabs.com test is, but it did report some
errors while testing the domain.

Let's Encrypt certs can work in Debian's and Guix's wget. I could `wget
--https-only` from my domain with a Let's Encrypt cert with HTTP Strict
Transport Security enabled.


> 
>       Mark
> 
> 
> 

  reply	other threads:[~2016-01-20  5:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 14:27 bug#22408: wget rejects Let's Encrypt certs, although Icecat accepts them Mark H Weaver
2016-01-20  5:03 ` Leo Famulari [this message]
2016-01-24 12:29   ` Ni* Gillmann
2017-03-05 21:05 ` Leo Famulari

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=20160120050349.GA5962@jasmine \
    --to=leo@famulari.name \
    --cc=22408@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).