From: Benjamin Zarzycki <ben@zarzycki.org>
To: wireguard@lists.zx2c4.com
Subject: macOS/darwin kernel module (kext)
Date: Mon, 15 Apr 2019 17:30:12 -0700 [thread overview]
Message-ID: <CALt6Z-Z2WvbZ8ru0W9Xqtgkmt_Oqwpq03=k1Y3r-BQPtXnbddA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 552 bytes --]
Hi Folks,
I'm new to the mailing list and community. If I missed some rules or
otherwise commit a faux pas, please let me know.
I searched the mailing list archives and didn't find any discussion of a
MacOS/darwin kernel module (kext) for WireGuard. I see it was implemented
using Apple's Network Extension API in the wireguard-ios repository and
there's the wireguard-go implementation as well.
I'm not an expert. Would anyone care to share their thoughts/opinions on
using Darwin's Network Kernel Extensions to implement WireGuard?
Thanks,
Ben
[-- Attachment #1.2: Type: text/html, Size: 1102 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-05-06 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALt6Z-Z2WvbZ8ru0W9Xqtgkmt_Oqwpq03=k1Y3r-BQPtXnbddA@mail.gmail.com' \
--to=ben@zarzycki.org \
--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).