From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Andrej Mihajlov <and@mullvad.net>
Cc: David Crawshaw <crawshaw@tailscale.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard is broken on iOS 15 beta
Date: Fri, 11 Jun 2021 10:50:57 +0200 [thread overview]
Message-ID: <CAHmME9qXs=ct-RNm0eGwu7mTdM+mCoNiYcJOOe5te=9n1ScC5g@mail.gmail.com> (raw)
In-Reply-To: <3BD85DF3-A8B2-45BF-A78C-D03524A226DC@mullvad.net>
Can I infer from that that your technique didn't work? Some
confirmation one way or another there would be useful, so I know
whether to dedicate some RE time next week to it or not. If I can
avoid the fd iteration, I'd prefer that.
Jason
next prev parent reply other threads:[~2021-06-11 8:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 11:44 Andrej Mihajlov
2021-06-10 11:51 ` Jason A. Donenfeld
2021-06-10 15:39 ` Jason A. Donenfeld
2021-06-10 22:33 ` David Crawshaw
2021-06-11 7:16 ` Andrej Mihajlov
2021-06-11 7:53 ` Jason A. Donenfeld
2021-06-11 8:42 ` Andrej Mihajlov
2021-06-11 8:50 ` Jason A. Donenfeld [this message]
2021-06-11 9:02 ` Andrej Mihajlov
2021-06-11 9:09 ` Jason A. Donenfeld
2021-06-16 13:25 ` Andrej Mihajlov
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='CAHmME9qXs=ct-RNm0eGwu7mTdM+mCoNiYcJOOe5te=9n1ScC5g@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=and@mullvad.net \
--cc=crawshaw@tailscale.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).