From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 46346C433EF for ; Wed, 2 Mar 2022 13:06:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235996AbiCBNHQ (ORCPT ); Wed, 2 Mar 2022 08:07:16 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42814 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236090AbiCBNHP (ORCPT ); Wed, 2 Mar 2022 08:07:15 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 64C79C3C1D for ; Wed, 2 Mar 2022 05:06:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1646226389; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/0fMnk0i2vLioTpWExJ0LC4UAikEb9oOUvO98xL5/80=; b=SO011vNhWBHn0yEPPWhkBEtLYU1g5wgprp2pQgIb79QKiy0MpnKBs0Kx6LYVK5JjPt9NPF yjN0Om75V5BWoYOjSqSrcfEVVUgrK0/ZWec546zYnN/JJAxvDPyF1zB83h6frFgJ1i5Tia 5ajklTwySoJ9//d5XUXH3ztiTlag4aM= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-457-jE-AZW4sPKW6CvKtvH_79g-1; Wed, 02 Mar 2022 08:06:23 -0500 X-MC-Unique: jE-AZW4sPKW6CvKtvH_79g-1 Received: by mail-wm1-f70.google.com with SMTP id f189-20020a1c38c6000000b0037d1bee4847so1886261wma.9 for ; Wed, 02 Mar 2022 05:06:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=/0fMnk0i2vLioTpWExJ0LC4UAikEb9oOUvO98xL5/80=; b=lh+lVHfm3/1H7m9IncsBf2mqcQO/OqVrGOUQMtgox/o2yAx6GZU31DMR9Xddd1UMSe dn0tC/nOGshGzpdmaMv70pYC8Q9Bq+TDt3d1I2JiWtbT/f+01m0OfzyrEG3hDNCVavbN ShPRHd/g+iRi+K1LoxhAhuyJUbTVVghNHyGQ7HRHjj0FDdRxfyYrtP+rr0nwF8m2IbHf urMRhHFsvwK9PGhs1O4gmI+IOvdJ4AFNgD3904rBW+14gOEHXAiSfa5g7bHy6uTLsyt+ FqEfhmI1WZgS9YVrNpHU4ITFRo9a4NEQYyLRgid/S+tZl5trOS/Cdj34MtszhFHUjFdx CP4g== X-Gm-Message-State: AOAM533AMkFYlQE29hegX+7jva636XeeSihXFODJ3TjJXJK37DQseKT0 2FLB25U3SaU1+OzLtIxU0gxCQiebdOcej4nAda7cpZ+PI/hnLzRwCqj/9vEfEW2yE69yRHP41Bk Ri/NSFuGXF3YQDI9H X-Received: by 2002:a05:600c:602a:b0:381:4245:ec26 with SMTP id az42-20020a05600c602a00b003814245ec26mr17603281wmb.25.1646226380004; Wed, 02 Mar 2022 05:06:20 -0800 (PST) X-Google-Smtp-Source: ABdhPJw1+nJ+l+dkYyyuQOpSfQyIgX1YDsaGTdYillGKYMXZjSRwlRMKKCr6zJiD+Ls1nk7mSP8fFg== X-Received: by 2002:a05:600c:602a:b0:381:4245:ec26 with SMTP id az42-20020a05600c602a00b003814245ec26mr17603270wmb.25.1646226379803; Wed, 02 Mar 2022 05:06:19 -0800 (PST) Received: from redhat.com ([2a10:8006:355c:0:48d6:b937:2fb9:b7de]) by smtp.gmail.com with ESMTPSA id v25-20020a05600c215900b0038117f41728sm5583452wml.43.2022.03.02.05.06.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 02 Mar 2022 05:06:18 -0800 (PST) Date: Wed, 2 Mar 2022 08:06:16 -0500 From: "Michael S. Tsirkin" To: "Jason A. Donenfeld" Cc: LKML , Linux Crypto Mailing List , Netdev , Alexander Graf , Jann Horn , Greg KH , Dominik Brodowski , Theodore Ts'o , Jakub Kicinski Subject: Re: [PATCH 3/3] wireguard: device: clear keys on VM fork Message-ID: <20220302075957-mutt-send-email-mst@kernel.org> References: <20220301231038.530897-1-Jason@zx2c4.com> <20220301231038.530897-4-Jason@zx2c4.com> <20220302033314-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, Mar 02, 2022 at 12:44:45PM +0100, Jason A. Donenfeld wrote: > Hi Michael, > > On Wed, Mar 2, 2022 at 9:36 AM Michael S. Tsirkin wrote: > > Catastrophic cryptographic failure sounds bad :( > > So in another thread we discussed that there's a race with this > > approach, and we don't know how big it is. Question is how expensive > > it would be to fix it properly checking for fork after every use of > > key+nonce and before transmitting it. I did a quick microbenchmark > > and it did not seem too bad - care posting some numbers? > > I followed up in that thread, which is a larger one, so it might be > easiest to keep discussion there. My response to you here is the same > as it was over there. :) > > https://lore.kernel.org/lkml/CAHmME9pf-bjnZuweoLqoFEmPy1OK7ogEgGEAva1T8uVTufhCuw@mail.gmail.com/ > > Jason Okay. The reason to respond here was since this is the user of the interface. Maybe unite the patchsets? Thanks, -- MST