From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Sune Mølgaard" <sune@molgaard.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Hooks in clients?
Date: Fri, 13 Nov 2020 16:50:52 +0100 [thread overview]
Message-ID: <CAHmME9qVUvad__o+MWvx9y_JPfqpOhyK_ttwKvB+hoLMiACCCw@mail.gmail.com> (raw)
In-Reply-To: <6bfa482b-42ee-ebc3-f2cb-4f52d9d2e219@molgaard.org>
wg-quick-based clients have this, but the UI clients do not.
However, for your use case, port knocking, I'd recommend getting rid
of the port knocking. WireGuard is silent to unauthenticated packets,
which means you don't need to port knock it. It was specifically made
as a port knocking replacement.
next prev parent reply other threads:[~2020-11-13 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 15:46 Sune Mølgaard
2020-11-13 15:50 ` Jason A. Donenfeld [this message]
2020-11-13 16:58 ` Nicholas Capo
2020-11-14 9:55 ` Sune Mølgaard
2020-11-14 10:02 ` 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=CAHmME9qVUvad__o+MWvx9y_JPfqpOhyK_ttwKvB+hoLMiACCCw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=sune@molgaard.org \
--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).