From: Andrej Mihajlov <and@mullvad.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
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 11:02:40 +0200 [thread overview]
Message-ID: <8A754E6A-6D25-427E-AF60-4AF9A61DF1B7@mullvad.net> (raw)
In-Reply-To: <CAHmME9qXs=ct-RNm0eGwu7mTdM+mCoNiYcJOOe5te=9n1ScC5g@mail.gmail.com>
My approach worked too. However it relies on the private interfaces of NetworkExtension framework, which we’d probably want to avoid.
In short it can be expressed in one line as:
let fd = packetFlow.perform(Selector("interface")).toOpaque().advanced(by: 0x128).assumingMemoryBound(to: Int32.self).pointee
But I bet that walking over fds is much safer.
Cheers,
Andrej
> On 11 Jun 2021, at 10:50, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> 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 9:02 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
2021-06-11 9:02 ` Andrej Mihajlov [this message]
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=8A754E6A-6D25-427E-AF60-4AF9A61DF1B7@mullvad.net \
--to=and@mullvad.net \
--cc=Jason@zx2c4.com \
--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).