Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Barry Scott <barry@barrys-emacs.org>
To: Sean Baildon <sean@baildon.co>
Cc: wireguard@lists.zx2c4.com
Subject: Re: macOS Catalina failing https
Date: Sun, 1 Mar 2020 08:55:35 +0000	[thread overview]
Message-ID: <0E67F928-58C9-4F00-A55E-7DD2A25D34AB@barrys-emacs.org> (raw)
In-Reply-To: <CAAF+QM=2cF9nV2Fq-HbUrbFbNwzw51FqAcG6RBvXv-07YWmp5Q@mail.gmail.com>



> On 27 Feb 2020, at 16:46, Sean Baildon <sean@baildon.co> wrote:
> 
> Hey,
> 
> Recently purchased and upgraded a new MBP to Catalina.
> 
> Requests to https enabled sites over the VPN no longer work, even
> using my old configuration. Requests to insecure sites—ex.
> http://example.com—work just fine.
> 
> My iOS devices work as expected. I've tried using the iOS
> configurations on the laptop, but it's the same behaviour; hanging.
> 
> I'm using the Mac App Store version of wireguard on a vanilla install
> of macOS Catalina. Are there any known issues? Happy to provide any
> useful debug

I just noticed that I tested with /opt/local/bin/curl not /usr/bin/curl.

Both worked. For completeness here is the start of the curl --verbose
that shows the certificate store that is used:

$ /usr/bin/curl --verbose https://example.com
*   Trying 93.184.216.34...
* TCP_NODELAY set
* Connected to example.com (93.184.216.34) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none

Barry


> 
> Thanks,
> Sean
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  parent reply	other threads:[~2020-03-03 23:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 16:46 Sean Baildon
2020-03-01  7:08 ` Eiji Tanioka
2020-03-01  8:44 ` Barry Scott
2020-03-01  8:55 ` Barry Scott [this message]
2020-03-01 12:11 ` Rémi Lapeyre
2020-03-01 22:28 ` Andrew Long

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=0E67F928-58C9-4F00-A55E-7DD2A25D34AB@barrys-emacs.org \
    --to=barry@barrys-emacs.org \
    --cc=sean@baildon.co \
    --cc=wireguard@lists.zx2c4.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).