From: Nicolas CAPEYRON <nicolas@capeyron.fr>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard on macOS stopped working after 1.0.10 update
Date: Thu, 17 Dec 2020 23:34:45 +0100 [thread overview]
Message-ID: <CAAhtBmPe58GJX1s2c+9fNvNEbzsfcYOp2Dm63UjGh1QRSfXU2Q@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qCRWXMVjuz6g6M0wMvhj9v90sTkHNOFCr+Jht-rUNFoQ@mail.gmail.com>
It's OK for me
Thank you very much
--
Nicolas CAPEYRON
Conseil en hébergement, architecture infra web
06 26 12 27 17 - https://www.sysadminbadass.com
--
Nicolas CAPEYRON
Conseil en hébergement, architecture infra web
06 26 12 27 17 - https://www.sysadminbadass.com
Le jeu. 17 déc. 2020 à 23:06, Jason A. Donenfeld <Jason@zx2c4.com> a écrit :
>
> Hi list,
>
> To provide an update on this issue:
>
> On Thu, Dec 17, 2020 at 2:43 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> > I'm really very sorry about this regression. I fixed it earlier today
> > already here: https://git.zx2c4.com/wireguard-apple/commit/?id=20bdf46792905de8862ae7641e50e0f9f99ec946
> > but now we're stuck having to wait for Apple's review of the fix. This
> > is as frustrating for me as it is for you.
>
> The macOS update went through, and version 1.0.11 is now available
> from the App Store. In my tests, this fixes the issue, but some
> confirmation from list subscribers is always helpful.
>
> However, they rejected the iOS update, due to the link in the version
> info window to https://www.wireguard.com/donations/ that we've had on
> there for two years. You can see their rejection here:
> https://data.zx2c4.com/apple-asks-me-to-remove-donation-link-from-app.png
> https://data.zx2c4.com/the-screenshot-that-apple-provided.png
>
> Not wanting to hold up getting this fix deployed, I quickly removed
> the link and resubmitted to the App Store:
> https://git.zx2c4.com/wireguard-apple/commit/?id=a4fc0f64b8bca8afae5abab37b81ba0b45836975
>
> So now the process of getting that fix deployed on iOS starts from the
> beginning again. It could take another 24 hours. It could take a full
> month. The process is opaque, and try as I may, I don't know what else
> I can do to get the fix out faster.
>
> And again, I'm really very sorry about the regression in the code, and
> that we didn't catch it earlier. I hope the update gets deployed to
> you all sooner rather than later.
>
> Jason
next prev parent reply other threads:[~2020-12-17 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 23:52 WireGuard on macOS stopped working after 1.0.10 update Glenn Schmidt
2020-12-17 1:43 ` Jason A. Donenfeld
2020-12-17 2:09 ` Glenn Schmidt
2020-12-17 21:53 ` Jason A. Donenfeld
2020-12-17 22:34 ` Nicolas CAPEYRON [this message]
[not found] ` <CAA6-MF8ZZ1eD+7wTfgzuGaiw8JPM+WiivJ0CxBja3-GZ=GXMaA@mail.gmail.com>
2020-12-18 9:19 ` Jason A. Donenfeld
2020-12-18 23:53 ` Jason A. Donenfeld
2020-12-19 0:11 ` Jacob Lambert
2020-12-19 10:40 ` Jason A. Donenfeld
2020-12-17 15:19 Nicolas CAPEYRON
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=CAAhtBmPe58GJX1s2c+9fNvNEbzsfcYOp2Dm63UjGh1QRSfXU2Q@mail.gmail.com \
--to=nicolas@capeyron.fr \
--cc=Jason@zx2c4.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.