From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by hurricane.the-brannons.com (Postfix) with ESMTP id 88A5F78B86 for ; Tue, 23 Sep 2014 09:43:44 -0700 (PDT) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta09.westchester.pa.mail.comcast.net with comcast id ufTv1o00317dt5G59gjj4A; Tue, 23 Sep 2014 16:43:43 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by omta13.westchester.pa.mail.comcast.net with comcast id ugji1o00e5LMg213Zgjiy6; Tue, 23 Sep 2014 16:43:43 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Tue, 23 Sep 2014 12:42:21 -0400 Message-ID: <20140823124221.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1411490623; bh=UIPE6JbO92HyIlUw/cTI+faw0bjJx7DF8LtDsArMkpM=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=bCKcdqvbwxPT+dkjC2/cf2pHucKBWnecfCwEQ+otV7Pvv09YjCEjown91mZMSZmRa A7oUL/rrTwaxUJl0sCMeKFCYQrhqkT0BnXZRJw0eE9zVIpjdrPowNkENziDnzFt5oH Rn0ucJsJQsu0KPfGpD0qPHZaEquBnAb/BnvXuS7zbkO0UTXlX+5mWNGTUoOgm+AXgy PfzicZlU4Bb3N8HbY6tMFys7PFmOUZkYt3/flyJewIoevjlSr/xDClnA27BjEtw+cf G25pkc5iaqsKIg9dghyYiJ7XqQjQBFQ9yknLRLp8+qZT+NrCr6vSiHIatd1JUto0QL s99ijfFm6e+YA== Subject: [Edbrowse-dev] Debian X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 16:43:44 -0000 > 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. Karl Dahlke