edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] building on ubuntu
Date: Tue, 3 Sep 2019 07:52:10 +0200	[thread overview]
Message-ID: <20190903055210.GA9581@nautica> (raw)
In-Reply-To: <20190802201727.eklhad@comcast.net>

Karl Dahlke wrote on Mon, Sep 02, 2019:
> > I do not exactly understand your 'gnutls' vs 'openssl'...
> Guess what, neither do I.
> We convinced ourselves a year ago that was the problem, but ldd clearly shows my curl linking to openssl, and
> curl https://weloveanimals.me
> fails on my machine; I switch to another machine, still curl + openssl, and it works.
> So we still don't understand it at all.
> I wish we did.

Hmm, I thought it could be that debian raised the minimum tls version in
/etc/ssl/openssl.cnf a year ago or two (MinProtocol = TLSv1.2 in
[system_default_sect] section of the file), but that website appears to
support older protocols as well if I try to force these with the openssl
s_client command...

I can connect to it just fine using gnutls-cli as well so it might be
something specific to a precise version of debian (tested on a
recent-ish buster).
Possibly the certificate authority (CA) that this website uses is not
bundled by debian? But then I don't see what rebuilding curl would help
you with in that case, Kevin might have had a different issue that
needed him to rebuild curl.


      reply	other threads:[~2019-09-03  6:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  6:32 Kevin Carhart
2019-09-02  7:27 ` Karl Dahlke
2019-09-02 16:13   ` Kevin Carhart
2019-09-02 19:24     ` Geoff McLane
2019-09-03  0:17       ` Karl Dahlke
2019-09-03  5:52         ` Dominique Martinet [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190903055210.GA9581@nautica \
    --to=asmadeus@codewreck.org \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* 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).