From: Nicholas Capo <nicholas.capo@gmail.com>
To: "Sune Mølgaard" <sune@molgaard.org>, wireguard@lists.zx2c4.com
Subject: Re: Hooks in clients?
Date: Fri, 13 Nov 2020 10:58:02 -0600 [thread overview]
Message-ID: <a47de6a45010b55c2ddab84e401a81a02f7728bd.camel@gmail.com> (raw)
In-Reply-To: <6bfa482b-42ee-ebc3-f2cb-4f52d9d2e219@molgaard.org>
On Fri, 2020-11-13 at 16:46 +0100, Sune Mølgaard wrote:
> Hiya,
>
> I am looking towards deploying WireGuard as my primary VPN
> connection,
> and wonder a bit if the various clients (Android, wg-quick, whatever
> there is for macOS, iOS and Windows), could be made to include the
> possibility of calling external programs upon (re-)connections, in my
> case specifically for port knocking, but possibly useful for other
> purposes as well?
>
> In the cases of Android and iOS, I am a bit unsure about interaction
> with other apps, so maybe, to begin with, just built-in port knocking
> capabilities could be considered.
>
> Any thoughts?
>
In my experence there isn't really a case where the client gets
disconnected (like a crash) and then needs to reconnect.
For me the client always stays enabled, but if there is a problem at
the remote end then packets don't go anywhere.
In other words the traffic might get dropped by the remote (feels like
no traffic *at all*), but I've never seen a situation where I was
accedentially sending unencrypted traffic.
Nicholas
next prev parent reply other threads:[~2020-11-14 9:59 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
2020-11-13 16:58 ` Nicholas Capo [this message]
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=a47de6a45010b55c2ddab84e401a81a02f7728bd.camel@gmail.com \
--to=nicholas.capo@gmail.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).