From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: nicolas prochazka <prochazka.nicolas@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [wireguard-dev] Ability to use one udp port for multiple wg interfaces
Date: Thu, 21 Sep 2017 17:36:52 +0200 [thread overview]
Message-ID: <CAHmME9oOCMcfkDxyMZ9rAqMd8Rwd2Zf6Dss5+QRDCp_3n1yxJA@mail.gmail.com> (raw)
In-Reply-To: <CADdae-g3cnKhOCECVZ-8nSv3vdxpzW61X8dQA0WSV0++dgP7JA@mail.gmail.com>
There shouldn't be any massive issue with sharing your public key
between customers. Just keep your private keys private.
prev parent reply other threads:[~2017-09-21 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 9:32 nicolas prochazka
2017-09-21 11:25 ` Jason A. Donenfeld
2017-09-21 11:46 ` nicolas prochazka
2017-09-21 11:54 ` Jason A. Donenfeld
2017-09-21 11:55 ` Jason A. Donenfeld
2017-09-21 12:17 ` nicolas prochazka
2017-09-21 12:54 ` Jason A. Donenfeld
2017-09-21 13:14 ` nicolas prochazka
2017-09-21 13:24 ` Jason A. Donenfeld
2017-09-21 15:29 ` nicolas prochazka
2017-09-21 15:36 ` Jason A. Donenfeld [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=CAHmME9oOCMcfkDxyMZ9rAqMd8Rwd2Zf6Dss5+QRDCp_3n1yxJA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=prochazka.nicolas@gmail.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).