From: Martin Schmiedecker <martin.schmiedecker@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Re: 34C3 - WireGuard Workshop?
Date: Mon, 18 Dec 2017 21:56:26 +0100 [thread overview]
Message-ID: <d240d132-c0e3-8ba1-f50b-accce83aa290@gmail.com> (raw)
In-Reply-To: <CAHmME9qVY2jiMoXGKYmfBSh4DD0tACZiV90RKqxw6SaunbaYLg@mail.gmail.com>
I'd be all in! Large setups would interest me, how to manage keys
efficiently and non-standard setups ...
Greetz, Martin
On 2017-12-18 19:52, Jason A. Donenfeld wrote:
> Hey guys,
>
> I'll be at 34C3. Is there any interest in having some sort of
> WireGuard workshop? Are there things to talk about it? Would this be
> fun or interesting? How many people would be interested in such a
> thing?
>
> Jason
>
>
> PS: still trying to work out hotel arrangements, if anybody knows any
> Leipzig tricks.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
next prev parent reply other threads:[~2017-12-18 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 18:52 Jason A. Donenfeld
2017-12-18 19:45 ` Georg Faerber
2017-12-18 20:56 ` Martin Schmiedecker [this message]
2017-12-20 16:11 ` Germano Massullo
2017-12-20 16:40 ` Markus Lindenberg
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=d240d132-c0e3-8ba1-f50b-accce83aa290@gmail.com \
--to=martin.schmiedecker@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).