edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Debian
Date: Tue, 23 Sep 2014 21:32:52 +0100	[thread overview]
Message-ID: <20140923203252.GC12972@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140823124221.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

On Tue, Sep 23, 2014 at 12:42:21PM -0400, Karl Dahlke wrote:
> > So the open question is whether CURLOPT_VERIFYHOST
> > should always match CURLOPT_VERIFYPEER?
> 
> Probably yes, as long as curl understands wild card certificates,
> wherein *.foobar.com matches www.foobar.com.
> I used such a certificate at my last job and it sure was convenient,
> and cheaper than buying a certificate for each subdomain.

I'd say the two should always match as well,
otherwise the behavior is counter-intuative (assuming curl treats the options separately)
particularly when using self-signed certs simply to get the encryption provided by ssl.
At the end of the day, when I switch off ssl verification I expect edbrowse to
behave like curl with the --insecure option, i.e.
do ssl regardless of whether the certificate can be verified.

Incidentally, the afore mentioned curl option works with the systems which
caused me to notice this bug.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-09-23 20:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 16:42 Karl Dahlke
2014-09-23 20:32 ` Adam Thompson [this message]
2014-09-24  4:54 ` Chris Brannon
2014-09-24 18:54   ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2014-09-24  7:13 Karl Dahlke
2014-09-21 21:19 Karl Dahlke
2014-09-22  5:53 ` Chris Brannon
2014-09-23 12:15   ` Adam Thompson
2014-09-23 14:56     ` Chris Brannon
     [not found] <mailman.8.1411327181.400.edbrowse-dev@lists.the-brannons.com>
2014-09-21 21:17 ` Chris Brannon
2014-09-21 21:20   ` MENGUAL Jean-Philippe
2014-09-23 12:23     ` Adam Thompson
2014-09-23 22:29       ` MENGUAL Jean-Philippe
2014-09-25 15:30       ` Chris Brannon
2014-09-25 17:23         ` MENGUAL Jean-Philippe
2014-03-08 20:40 [Edbrowse-dev] debian Karl Dahlke
2014-03-08 20:45 ` MENGUAL Jean-Philippe
2014-04-01 11:20   ` Adam Thompson
2014-04-01 16:24     ` MENGUAL Jean-Philippe
2014-04-15  9:02       ` Adam Thompson
2014-01-04 20:03 Karl Dahlke
2014-01-04 17:28 Karl Dahlke
2014-01-04 18:18 ` Chris Brannon

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=20140923203252.GC12972@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).