Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Aaron Jones <aaronmdjones@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Master's thesis about VPN performance featuring WireGuard
Date: Sat, 9 Mar 2019 06:52:02 +0000	[thread overview]
Message-ID: <08c7ef00-1e08-3f4c-8be8-731e16abfcd1@gmail.com> (raw)
In-Reply-To: <B00D5F62-9996-4A28-9DD3-28008C1B032A@net.in.tum.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/03/2019 16:37, Paul Emmerich wrote:
> Hi,
> 
> 
> one of my students wrote his Master's Thesis about performance of 
> VPN gateways.> The thesis features a performance comparison
> between Wireguard, OpenVPN, and Linux IPsec. He also implemented
> several different possible architectures for VPN gateways and draws
> some conclusions about possible improvements in Wireguard.
> 
> Like most good theses it was written under time pressure close to 
> the deadline, so there are some rough edges. Despite this I think 
> it's a quite excellent thesis that I'll be transforming it into a 
> (shorter) journal article later this year, but I've wanted to share
> the thesis with you hoping that it's helpful or interesting for
> some of you.

One of the rough edges is that it refers to peer identities as Ed25519
public keys, but they are in fact Curve25519 public keys; WireGuard
does not use an elliptic-curve signature scheme, but only
elliptic-curve Diffie-Hellman-Merkle key agreement.

- -- 
Aaron Jones

-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCgAdFiEEYKVBwe43zZh/jkxPivBzdIirMBIFAlyDYo8ACgkQivBzdIir
MBLrkRAAmxm460mBaN/VYmHCG/brgJxkoISeAj2QT6n+8X39NbL+LZWN9A4ZYiP9
3VnGCK/NQH1UVwI3GElT5S1XV0gAYw+BGaSC9a7qBoE4Ks5WwnrZHl5cuejYTD+t
uN6UOn0nQc5xyzCN++Da7cHJ2NbMOIHsTOTpApurmEMhpekSPtzZS4Px2OFEEmj1
R+1Sh+ygAEjVm8WjldLg+Uj1h/kybVvG8qlbe4ZSZinylM+k2qlfYdsZnttnjw7u
if3L900m0IixDhxhvUZJ52rNL55B8iHSIWuyzrO+Ikb+e+/e8iIcVox1n7GNIE8L
Vv1A+h55nsx1FFxNDWkTI5wGrg883HquIy5PH9AI4RWUK5ooDx/TJA04110dixIf
PVpuh4gpAlLTWuXVkm5LzgJ7Ys5l+qQkao0YYV0TXQpVdfuWaD8exlKO5pyjYagN
ppTsPIDh0Go2uVOUZuGzt3cCG8QHfrbo0xePWbQdc3PeMUbuDwU5aZoFmn2oHuWw
UafH381nFUsH35fmXG67PcZ5gme91ZrtaKGEof3cu/+Ylv9HU0mh6MbBjVI9PtNf
HD+FZF4FNUX6ekNf86mMgMSiONmzo+IcgjRwbfIT1p7AQ2Aox2D3jars/bD3q2/H
ohUW/YlzgQF4AQQmQ9ekXYrpmfKczMbTkO9znyayMENDofuNSHk=
=ukdC
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-03-09  6:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05 16:37 Paul Emmerich
2019-03-09  6:52 ` Aaron Jones [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=08c7ef00-1e08-3f4c-8be8-731e16abfcd1@gmail.com \
    --to=aaronmdjones@gmail.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).