From: wireguard@p-np.de
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuardKit for iOS and macOS Released
Date: Thu, 17 Dec 2020 09:31:21 +0100 (CET) [thread overview]
Message-ID: <1143670031.15228.1608193881153@office.mailbox.org> (raw)
In-Reply-To: <CAHmME9ozv2UAe8NOUaBGDfQpohYS+SLY+Zix8A-q3dt8AKao+w@mail.gmail.com>
That's really cool, thank you!
Christian
> Jason A. Donenfeld <jason@zx2c4.com> hat am 15.12.2020 17:06 geschrieben:
>
>
> Hi folks,
>
> For the last several weeks, Andrej from Mullvad has been working hard
> at modularizing the wireguard-apple repository, which contains the
> code we use to build WireGuard for macOS and WireGuard for iOS. The
> end result is WireGuardKit, an open source Swift PM package that
> anybody can use to easily build macOS and iOS applications that
> incorporate WireGuard tunnels. Instructions on usage are available
> here:
>
> https://git.zx2c4.com/wireguard-apple/about/#wireguardkit-integration
>
> Users of WireGuardKit will be able to instantiate a WireGuardAdapter
> inside of their PacketTunnelProvider network extension. The one that
> ships with WireGuard for macOS and iOS should serve as a simple
> reference of ~125 lines of boiler plate code:
>
> https://git.zx2c4.com/wireguard-apple/tree/Sources/WireGuardNetworkExtension/PacketTunnelProvider.swift
>
> All of the heavy lifting has moved into the WireGuardKit, so that
> application writers do not need to concern themselves with low-level
> networking details.
>
> In general, the WireGuardKit project has been a great example of
> positive collaboration between the WireGuard open source project and
> an industry stakeholder. As Mullvad's mobile apps depend on WireGuard,
> putting the development time into improving our upstream code so that
> their downstream code can more easily consume it, as well as
> contributing fixes and improvements in their downstream code back
> upstream, not only makes things easier for Mullvad, but also brings
> shared improvements to everyone else across the WireGuard ecosystem.
>
> As more developers begin to use WireGuardKit, we're very interested to
> hear feedback, particularly about missing features or APIs that might
> be useful.
>
> Enjoy!
> Jason
>
> PS: Today we've also sent new versions of the WireGuard app up to the
> App Store approval process for iOS and macOS, with a bunch of
> performance improvements and also support for Apple Silicon. Who knows
> how long it will take for Apple to approve it -- we've experienced
> wait times between 1 day and over 1 month -- but keep your eyes peeled
> for the update.
prev parent reply other threads:[~2020-12-17 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 16:06 Jason A. Donenfeld
2020-12-17 8:31 ` wireguard [this message]
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=1143670031.15228.1608193881153@office.mailbox.org \
--to=wireguard@p-np.de \
--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).