Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4331355imu; Mon, 7 Jan 2019 21:10:28 -0800 (PST) X-Google-Smtp-Source: ALg8bN5pDjr10FpFD1dSMhTf317PzG4UjGwnGGBOgM/akD49X6TihnE8/khWGqtpZmgvnlIyHVFJ X-Received: by 2002:a17:902:442:: with SMTP id 60mr325665ple.73.1546924228288; Mon, 07 Jan 2019 21:10:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546924228; cv=none; d=google.com; s=arc-20160816; b=bHWXFskx6arFLat4qDlIQdcV4P4ONvSZfbd9e2xfvOCbyQ9BwTEzPAzItEaD99dRRS cNDpTg9k/fKRHmS3Qfg8x9nsWPjOU63cCo0if5bjlJTo9XuNEDZIEDb0NOowJXwrV1DB a47N12JeoKrClmo5CWft2xgJgMIIuXoSaU9XTGIqFOuivd97j+J22AXkXhDs8nn0HSRw l0YICfc5mjvX2lyhMNaRbBTE8SZO3LUqoIHrcJWBTlY20d+OfL6SsuZNuzEoRTwfMvfu egBUKdOR3U6xDp7jwoCDvG+8vsnu13i3xmd7KGjKOOHonOIxslonkG15zomW9Rop+KKe IKPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=pGTaN4XS1hcPfGraYCqpF6nNE+ABtjQqxeFzGRO4KJI=; b=b7qijNqwVXcgwfj0jZLDP/BcSnRFyg6NXSdfAGK3WpVvTEqC4A0KeV8kMcGzM5nmmB uEOsGqfvb1ftyO2cd1mQPYDaj4BR27lGm+GOwDH7w/n6VfmNIHKGaDg7mJA+EsPemJvw XheA0VLjl1HcU1/C74ZayJRXFx9XOvxSYj/Q61yB6pyDVHaecT1feHtHZGwI69rJlQz7 47XDsrXacrB80c3v9GIL+JEz+8Wmu11SGcO8E6mKi9Vs3U6FwfljqJ/bn0C76sl5PpxO 50L0fb/kFYd7gCFRKuFybOuSYDfd+x5vPIPJbydDOVSiu8huG0iUKGe//F/EWJIq+O8d MNbw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q189si67978795pfb.62.2019.01.07.21.10.13; Mon, 07 Jan 2019 21:10:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727576AbfAHFEf (ORCPT + 99 others); Tue, 8 Jan 2019 00:04:35 -0500 Received: from orcrist.hmeau.com ([104.223.48.154]:54820 "EHLO deadmen.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725838AbfAHFEf (ORCPT ); Tue, 8 Jan 2019 00:04:35 -0500 Received: from gondobar.mordor.me.apana.org.au ([192.168.128.4] helo=gondobar) by deadmen.hmeau.com with esmtps (Exim 4.89 #2 (Debian)) id 1ggjYt-0000Ns-JJ; Tue, 08 Jan 2019 13:04:23 +0800 Received: from herbert by gondobar with local (Exim 4.89) (envelope-from ) id 1ggjYU-00055t-Le; Tue, 08 Jan 2019 13:03:58 +0800 Date: Tue, 8 Jan 2019 13:03:58 +0800 From: Herbert Xu To: Stephan Mueller Cc: "Lee, Chun-Yi" , "Rafael J . Wysocki" , Pavel Machek , linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, keyrings@vger.kernel.org, "Rafael J. Wysocki" , Chen Yu , Oliver Neukum , Ryan Chen , David Howells , Giovanni Gherdovich , Randy Dunlap , Jann Horn , Andy Lutomirski Subject: Re: [PATCH 1/5 v2] PM / hibernate: Create snapshot keys handler Message-ID: <20190108050358.llsox32hggn2jioe@gondor.apana.org.au> References: <20190103143227.9138-1-jlee@suse.com> <4539995.kc8yiMsNgQ@tauon.chronox.de> <20190107153327.GB4210@linux-l9pv.suse> <4499700.LRS4F2YjjC@tauon.chronox.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4499700.LRS4F2YjjC@tauon.chronox.de> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 07, 2019 at 04:52:00PM +0100, Stephan Mueller wrote: > > Would it make sense to polish these mentioned KDF patches and add them to the > kernel crypto API? The sprawl of key derivation logic here and there which > seemingly does not comply to any standard and thus possibly have issues should > be prevented and cleaned up. Are we going to have multiple implementations for the same KDF? If not then the crypto API is not a good fit. To consolidate multiple implementations of the same KDF, simply provide helpers for them. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt