From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Embedding WireGuard into Custom Applications
Date: Wed, 23 Dec 2020 17:33:45 +0100 [thread overview]
Message-ID: <CAHmME9pnwQMzZGjV+22NB-6K11f8W1U4vS-U1MDkABjRvucfQg@mail.gmail.com> (raw)
Hi,
As WireGuard adoption continues to accelerate, I'm getting more emails
asking me how to make custom WireGuard clients for specific use cases.
The most obvious inquiry has been from VPN providers looking to
integrate WireGuard into their branded clients, but there have also
been others looking to do more nuanced things.
To that end, I've put together a doc on this on the webpage:
https://www.wireguard.com/embedding/
This summarizes the current options for Windows, macOS, iOS, Android,
Linux, and so on. It mostly amounts to a series of links at the
moment, but I figure it's helpful to have a unified place for that.
If you have suggestions for expanding that, I'm all ears.
Jason
reply other threads:[~2020-12-23 16:34 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=CAHmME9pnwQMzZGjV+22NB-6K11f8W1U4vS-U1MDkABjRvucfQg@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).