From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] Threads (fwd)
Date: Sun, 01 Sep 2019 22:48:21 -0400 [thread overview]
Message-ID: <20190801224821.eklhad@comcast.net> (raw)
In-Reply-To: <f71d14ff-63c8-575a-a8f6-457adb1121e9@geoffair.info>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
Hi Geoff,
There are several questions here, this only addresses one of them.
The best bet is not to have certfile in your .ebrc config file at all.
If you don't specify, curl looks for it and probably finds it, because it was configured that way.
Only set certfile = if you need to override what curl does.
If the certificates are not found, for any reason, then any https connection will fail.
You can bypass this with the vs command.
vs
don't verify ssl connections.
Then nasa and everything else will work - though if you're logging into an https site to do your banking it is less secure, obviously.
Karl Dahlke
next prev parent reply other threads:[~2019-09-02 2:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 2:58 Kevin Carhart
2019-09-01 3:04 ` Karl Dahlke
2019-09-01 18:37 ` Geoff McLane
2019-09-02 2:48 ` Karl Dahlke [this message]
2019-09-02 18:38 ` Geoff McLane
2019-09-02 18:53 ` Karl Dahlke
-- strict thread matches above, loose matches on Subject: below --
2019-08-28 5:46 Kevin Carhart
2019-08-28 6:25 ` Karl Dahlke
2019-08-29 3:23 ` Kevin Carhart
2019-08-29 19:46 ` Geoff McLane
2019-08-29 21:05 ` Karl Dahlke
2019-08-30 19:23 ` Geoff McLane
2019-08-30 21:26 ` Karl Dahlke
2019-08-30 22:08 ` Karl Dahlke
2019-08-31 19:05 ` Geoff McLane
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=20190801224821.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/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).