From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id eba74b3e for ; Mon, 10 Jul 2017 01:43:00 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 7f72ac90 for ; Mon, 10 Jul 2017 01:43:00 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 22f59f77 for ; Mon, 10 Jul 2017 01:56:34 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id da7c7817 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Mon, 10 Jul 2017 01:56:33 +0000 (UTC) Received: by mail-wr0-f181.google.com with SMTP id c11so118448810wrc.3 for ; Sun, 09 Jul 2017 19:01:05 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20170710014834.GA14901@wolff.to> References: <20170710014834.GA14901@wolff.to> From: "Jason A. Donenfeld" Date: Mon, 10 Jul 2017 04:01:04 +0200 Message-ID: Subject: Re: Looks like 4.13 introduces a new incompatibility To: Bruno Wolff III Content-Type: text/plain; charset="UTF-8" Cc: WireGuard mailing list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hey Bruno, Thanks for the heads up. Does this fix it? https://git.zx2c4.com/WireGuard/commit/?id=dd007ad550b3def8a858e57aa718af9b00047a28 Jason