Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp254193imm; Wed, 4 Jul 2018 23:03:29 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfr+qh1VaOwe1zuGcEBm9byHEGeJVjrZe3EYFsJfrIPD5kE+0HB9CIb7GKTkKr8TqsiLup+ X-Received: by 2002:a63:f948:: with SMTP id q8-v6mr4217101pgk.292.1530770609266; Wed, 04 Jul 2018 23:03:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530770609; cv=none; d=google.com; s=arc-20160816; b=mpf6ta8bBuKE2rbQP8RHbHHlsFOQKxlsGyqXz7rPe93ZWY9dfRogvRRxxV3shXy9N1 7Zc0lz1p/OXaUkioVbfaNrHZanAoi7HoRnge0jEnUz+6FrYmw5rFcj0S1TA4PfRdyp1Q kSs6HLigO26TCNCX5OLlElmvhF7bpD4Fjh79osdP5BA1fvQcDR+BrwyTsGAEls7CdTtt BRnu53DgwztpM8uNS2SExFOnvCg6VC0c0C9x/gMZfUqS6vnLkVADCenfCPQB5IyNxp3z mQZMejx0q1bFbUdJIhgD8CRq7TwU4gCfdNDMbYsGVhjw92RAbEnZx5nyJY9edPUqg286 itLg== 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:dkim-signature:arc-authentication-results; bh=0bnqpZm6zOTwSyqPH4MsMtbg/4SQZh3rRphcKoxs4Yo=; b=k15uwG8fSTqGJevwmmqyC3FCBNjcw7afcwoIeIwIo7NTKsJt8oonYDQ9iwSS5n1d3L TlkObC9XnYN6DY9vy8fmGgUpDWmyQ8zIttV35jnwrfgj7Dr/SLuDNGzf0raKQwoY8TER OVJ2kPKpffnV74UFOpFWZt0I3WXT6plv8LrtWVbjjd+5Yt+YV6ZVt5QALfqcqUVXVRRD 8uVEA3GDN1Z5vVkJtVdy2YIAI6EnC4BcSrNX5p3MKWQzI6sQ9LpgjlqqHdf9OlDvVKDD bcxBljMvuHPXyvA7ODSTrMoQvjH1gWnK/ozh6sHbBylAyrACHiNd3tUsaowPzY1FzhMm 4axw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=T0+ta6QN; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i126-v6si5469238pfc.296.2018.07.04.23.03.14; Wed, 04 Jul 2018 23:03:29 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=default header.b=T0+ta6QN; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753397AbeGEGB2 (ORCPT + 99 others); Thu, 5 Jul 2018 02:01:28 -0400 Received: from mail.kernel.org ([198.145.29.99]:58606 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753271AbeGEGBX (ORCPT ); Thu, 5 Jul 2018 02:01:23 -0400 Received: from localhost (unknown [223.226.33.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E9F592417D; Thu, 5 Jul 2018 06:01:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1530770482; bh=gFJaGH6cBrJHX8uajhXZVxA/sy7ZT8chrMNIjP7Zkec=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=T0+ta6QN6ooOSSODju+9rpNrHxjKihj7xNXYCncaXJkGpL9wrYB5xqWgfKVjcBymn 3KO+zuGlD/MZF7O1hrDAoRLGEWiwsjGhHJ54AlXZ/8cENEo3V+4HDAgqKxZAdTLy2c 93mtaQWqf2WsHIK5tmDLm/YljdLp38APdkwnMak8= Date: Thu, 5 Jul 2018 11:31:14 +0530 From: Vinod To: Stephan Mueller Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, Bjorn Andersson , Matt Mackall , Herbert Xu , Arnd Bergmann , Greg Kroah-Hartman , linux-arm-msm@vger.kernel.org, Stephen Boyd , Timur Tabi Subject: Re: [PATCH v3 3/6] crypto: Add Qcom prng driver Message-ID: <20180705060114.GG22377@vkoul-mobl> References: <20180703060434.19293-1-vkoul@kernel.org> <20180703060434.19293-4-vkoul@kernel.org> <19909549.EUeuX9KOs7@tauon.chronox.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19909549.EUeuX9KOs7@tauon.chronox.de> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephan, On 04-07-18, 18:02, Stephan Mueller wrote: > Am Dienstag, 3. Juli 2018, 08:04:31 CEST schrieb Vinod Koul: > > +static int qcom_rng_seed(struct crypto_rng *tfm, const u8 *seed, > > + unsigned int slen) > > +{ > > + return 0; > > +} > > One more question: is it not possible to mix in data into the DRNG? I thought > it would be possible with the Qualcomm DRBG. > > Note, I am asking because of my /dev/random drop-in-replacement > implementation, any RNG from the kernel crypto API can be configured to be > used as an output DRNG. Though, this will only work if the DRNG also accepts > seed from the software noise sources. The v1 hardware supports seeding but the register is Read Only for SW and only trusted zone (firmware) can write. v2 hardware slice does not have seeding. v2 seeding is not accessible to SW. So in short, it is not available for us to use :( -- ~Vinod