From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: WireGuard for macOS
Date: Sat, 16 Feb 2019 02:26:20 +0100 [thread overview]
Message-ID: <CAHmME9qjTJbWYVr9cToXpfnshGkppcqVS5=iVzqsrjS+v_aF+w@mail.gmail.com> (raw)
Hey everyone,
After many months of hard work, Roopesh, Eric, and I are pleased to
announce an initial version of WireGuard for macOS:
https://itunes.apple.com/us/app/wireguard/id1451685025?ls=1&mt=12
This is built from the same code base as our existing iOS app and
makes use of Apple's Network Extension API to provide native
integration into the operating system's networking stack. The
application lives in the status bar, and after importing a
configuration, the ordinary System Preferences networking item may
also be used to control each tunnel. Because it uses these deep
integration APIs, we're only allowed to distribute the application
using the macOS App Store (whose rejections, appeals, and eventual
acceptance made for quite the stressful saga over the last week and a
half). Compared to the current CLI integration, we expect the
WireGuard experience using this app to be excellent.
For curious folks without a Mac (or without the patience to cajole KVM
into booting macOS), I've assembled a few screenshots:
https://data.zx2c4.com/wireguard-for-macos-screenshots-february-2019/
This is new software, and there will certainly be problems. Don't
hesitate to email team@wireguard.com directly with bugs as you
encounter them.
Enjoy!
Regards,
Jason
PS: Because people will inevitably ask: yes, a Windows client is on
its way, and it will have a very similar interface to this macOS one.
We're taking the long and careful route, writing a new TUN driver for
Windows 7+ called "Wintun" that we expect to be safer and faster than
the current popular OpenVPN TUN driver, and also suitable for all
projects, not just for WireGuard. We already have packets flowing and
things generally work well, but polish will require a bit of patience.
If you'd like to help and have an appetite for NDIS drivers, Win32 GUI
programming, or Go, please do get in touch.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-02-16 1:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 1:26 Jason A. Donenfeld [this message]
2019-02-17 19:05 ` Le Sandie
2020-03-07 17:03 tormen
2020-03-08 2:37 ` Ben Hyde
2020-03-08 4:18 ` Eiji Tanioka
2020-03-21 21:45 ` Johnny Utahh
2020-03-30 2:22 ` Jason A. Donenfeld
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='CAHmME9qjTJbWYVr9cToXpfnshGkppcqVS5=iVzqsrjS+v_aF+w@mail.gmail.com' \
--to=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).