From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: Bzzzz <lazyvirus@gmx.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Can't seem to split tunnel using tables the way I can in OpenVPN
Date: Thu, 25 May 2017 19:58:19 +0200 [thread overview]
Message-ID: <CAKXLc7cf-XW=-yeSDPQbDaKhHmKrj3Tb+n_jv4GLUt_k+qg1xg@mail.gmail.com> (raw)
In-Reply-To: <20170525191337.696cd9d5@msi.defcon1>
On Thu, May 25, 2017 at 7:13 PM, Bzzzz <lazyvirus@gmx.com> wrote:
> And BTW, it is much more dangerous to reveal your keys on the Ternet
> than your endpoint IP address=E2=80=A6
>
That just made my day, LoL! I could not help posting it on twitter:
https://twitter.com/thinrope/status/867801802724569088
Kalin.
next prev parent reply other threads:[~2017-05-25 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 23:04 Text Editor
2017-05-25 17:13 ` Bzzzz
2017-05-25 17:58 ` Kalin KOZHUHAROV [this message]
2017-05-25 18:11 ` Bzzzz
2017-05-25 19:14 ` Kalin KOZHUHAROV
2017-05-25 19:28 ` Bzzzz
2017-05-25 19:32 ` David Woodhouse
2017-05-25 19:45 ` Bzzzz
2017-05-25 19:50 ` David Woodhouse
2017-05-25 20:03 ` Bzzzz
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='CAKXLc7cf-XW=-yeSDPQbDaKhHmKrj3Tb+n_jv4GLUt_k+qg1xg@mail.gmail.com' \
--to=me.kalin@gmail.com \
--cc=lazyvirus@gmx.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).