edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Geoff McLane <ubuntu@geoffair.info>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] building on ubuntu
Date: Mon, 2 Sep 2019 21:24:07 +0200	[thread overview]
Message-ID: <d7ea0f15-c2d4-9e24-5f73-a1bcb91ba68b@geoffair.info> (raw)
In-Reply-To: <alpine.DEB.2.21.1909020910430.37989@phoenix>

Hi Karl,

I do not exactly understand your 'gnutls' vs 'openssl'...

My Ubuntu 18.04.3 LTS sports -
~/Documents/edbrowse$ curl --version
curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 
zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 
Release-Date: 2018-01-24
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps 
pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM 
NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL

which specifically mentions 'OpenSSL/1.1.1'...

And using $ ldd /usr/bin/curl ... for SSL it shows -
     libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 

And more ~/Documents/edbrowse$ openssl version
OpenSSL 1.1.1  11 Sep 2018

So unsure where 'gnutls' comes into this...

As reported -
  $ curl https://weloveanimals.me
seems to work fine for me...

But, yes Kevin, having `a little knowledge base going` is always a good 
be it emails, lists, issues, README, google, whatever... It is always 
how to organize,
such that 'it' can be found, remembered, when next encountered... that 
is identifying
the 'it'...

Regards, Geoff.

  reply	other threads:[~2019-09-02 19:24 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 [this message]
2019-09-03  0:17       ` Karl Dahlke
2019-09-03  5:52         ` Dominique Martinet

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=d7ea0f15-c2d4-9e24-5f73-a1bcb91ba68b@geoffair.info \
    --to=ubuntu@geoffair.info \
    --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).