Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Matthew Poletiek <matthew.poletiek@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WARNING - iOS 15] Update WireGuard to >=1.0.15-26 *before* updating to iOS 15
Date: Fri, 15 Oct 2021 14:58:41 -0500	[thread overview]
Message-ID: <CAJhSV8uZ3nGOL9-oUu=wL1CiY7Eeux0UYzsL4psMWeR1D73VMQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9p9XxAhh4WgZgRiMRFxahp2wabPr-KuW=AdVQyRsHaD+A@mail.gmail.com>

Hi,

Thanks for the update Jason.

Unfortunately I wasn't reading and didn't prepare properly. In XCode,
does anyone know the best way to upgrade the wireguard-apple package
so my custom app can leverage the latest fixes?

Thanks again,
-------------------------------------------
Matthew Poletiek
303.810.9082
matthew.poletiek@gmail.com
www.matthewpoletiek.com



On Thu, Sep 23, 2021 at 9:25 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hello list,
>
> Due to buggy changes Apple has made to the Keychain on iOS 15, older
> versions of WireGuard on iOS will *eat your VPN configurations* when
> upgrading to iOS 15. This has been fixed by [1], which is now
> available as of version ≥1.0.15-26. If you are still on iOS 14, before
> updating to iOS 15, please remember to update the WireGuard app to
> this latest version in the App Store.
>
> Sorry for the hassle.
>
> Jason
>
> [1] https://git.zx2c4.com/wireguard-apple/commit/?id=03a59ff38e96fb3bb5dde2f15fe42198d1dfb995

  reply	other threads:[~2021-10-15 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24  2:23 Jason A. Donenfeld
2021-10-15 19:58 ` Matthew Poletiek [this message]
2021-10-15 21:17   ` Matthew Poletiek

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='CAJhSV8uZ3nGOL9-oUu=wL1CiY7Eeux0UYzsL4psMWeR1D73VMQ@mail.gmail.com' \
    --to=matthew.poletiek@gmail.com \
    --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 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).