Deterministic Cryptographically Authenticated Network Signatures on Windows NLA

Ivan Labáth labawi-wg at
Tue Jul 2 22:47:53 CEST 2019

Hi Jason,

while the idea of Deterministic Cryptographically Authenticated
Network Signatures is commendable, what is the *purpose* of the
network signature in Windows?

On Fri, Jun 28, 2019 at 10:15:39PM +0200, Jason A. Donenfeld wrote:
> On Fri, Jun 28, 2019 at 6:33 PM zrm <zrm at> wrote:
> > The drawback of this approach is that if anything in the configuration
> > changes at all, it becomes a different network. In theory that's the
> > idea, but in practice changes to the configuration will sometimes happen
> > that shouldn't change which network it is.
> No, that's the entire point. If you change your network configuration
> -- which public keys (identities) are allowed to send what traffic,
> then this should not map to collided network signature. You're free to
> configure Windows to apply the same network profile and conditions to
> a variety of network signatures, of course.

What would the procedure be when tweaking/changing the configuration
of the interface? If e.g. peer changes key, added ip, removed ip,
renumbered ip, ... some other trivial change. The more peers you have,
the more changes you have.

Using id from either local priv/pub key, interface name, both,
or possibly a config item seems most reasonable to me.

IMO, if you reuse the same key for different networks, then you are
shooting yourself in the foot, so it is a sufficient identifier.
Add short warning to documentation if appropriate:
"Interface public key is used as the network identifier in Windows.
Its reuse will reuse settings of e.g. firewall."


More information about the WireGuard mailing list