From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: matthias@urlichs.de Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id f16d1362 for ; Thu, 17 May 2018 05:53:56 +0000 (UTC) Received: from netz.smurf.noris.de (mail.vm.smurf.noris.de [IPv6:2001:780:107:8:83::]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 61dd2b6a for ; Thu, 17 May 2018 05:53:56 +0000 (UTC) Subject: Re: Need for HW-clock independent timestamps To: wireguard@lists.zx2c4.com References: <793381ba-b59d-50e4-6d7b-cbe9bef91ba1@cgws.de> <489c2f57-574a-1223-9c4d-266904e52c94@gmail.com> <20180515202126.yw57deh6st5ebnk6@kowloon> <20C72316-B8FC-4515-8DC8-8BC82BF3864F@cgws.de> <1526528456.18498.0@mail.makrotopia.org> <20180517100325.1c542b1f@natsu> From: Matthias Urlichs Message-ID: <748e7dbf-0238-6c81-ab18-83d6174405fe@urlichs.de> Date: Thu, 17 May 2018 07:53:17 +0200 MIME-Version: 1.0 In-Reply-To: <20180517100325.1c542b1f@natsu> Content-Type: text/plain; charset=utf-8 List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 17.05.2018 07:03, Roman Mamedov wrote: > Personally I am puzzled this is even an issue in WG. Not a single other VPN > protocol mandates every node to keep a monotonically increasing counter, > including even over reboots. Wireguard's connection setup is a whole lot simpler than most other protocols. It basically doesn't require a "real" handshake, just a request/reply pair. Thus it's vulnerable against disruption by replay attacks – a replayed rekey packet would disrupt conversation until the real sender times out, a minute later. -- -- Matthias Urlichs