From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Deterministic Cryptographically Authenticated Network Signatures on Windows NLA
Date: Wed, 3 Jul 2019 07:42:35 +0200 [thread overview]
Message-ID: <53894a06-1d80-ea2c-7c75-1b5c8b5bc512@urlichs.de> (raw)
In-Reply-To: <20190702204753.GA20367@matrix-dream.net>
On 02.07.19 22:47, Ivan Labáth wrote:
> while the idea of Deterministic Cryptographically Authenticated
> Network Signatures is commendable, what is the *purpose* of the
> network signature in Windows?
The network signature's purpose depends on your network policy. For some
it's a strict "this network requires that firewalling and access policy
and whatnot", for others it's a far more fluid concept.
Thus, if you're in the latter situation and you use some program that
changes your WG setup, that same program can associate the new signature
with the existing rules, assuming it has the rights to do so. Problem
solved.
--
-- Matthias Urlichs
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-07-03 5:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 14:26 Jason A. Donenfeld
2019-06-28 16:25 ` zrm
2019-06-28 20:15 ` Jason A. Donenfeld
2019-07-02 20:47 ` Ivan Labáth
2019-07-03 5:42 ` Matthias Urlichs [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=53894a06-1d80-ea2c-7c75-1b5c8b5bc512@urlichs.de \
--to=matthias@urlichs.de \
--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).