Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp411662imw; Wed, 13 Jul 2022 00:08:41 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tGF0ny43XYIC33g2zXi7LH8QmOUzPBYHow8S/xZH2QfBe8femm32U8XwZr51Yee337XJwK X-Received: by 2002:a17:902:bc45:b0:16b:d5bf:c465 with SMTP id t5-20020a170902bc4500b0016bd5bfc465mr1867625plz.128.1657696120819; Wed, 13 Jul 2022 00:08:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657696120; cv=none; d=google.com; s=arc-20160816; b=tWs6Zd18giv9NloL/mJQcU76HxkPPBNLx6imm07c63loJja3weGHJdl66nhnNjx9CC mwoefl2f+CePf1ASMUQlNz5b4TAowH+U3jaOG6LFEH0BqGfIlwPxlc0PKhel1ZEILdeN f5PcGy8B/mG8Ep/K8qYYfPox3dxRDXyFVPhvt413wjBib2s3LqCrXPD1YSEip1tf1SM0 tBN5k+jEqbVArPmMOtJP1Dv5Dtp1qKddZNGIKche4UMPvCHk2qebdbIahTlcYv4gaRKb YLTcuR29z1tU/0IPKlRURPW3/CYjq8RjoxBc9Q/U/n5uCs1urp0N8a6rMBI8W25n5d75 xjLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=n7mQQpkSKyBeUuYBLyboh7IsO0uahzQ+El0fPXZP7kw=; b=DXq3kq+4I2SK61MOldBsvm8h2x0ecSzvXDsmxa+oaeSPXwDKuMZFxEubWpuj1wVQmA UWCICyKVYyYZMwYec24HIJpX7QwNeQWaWI0uFRRWz3r6va0JF5rxg5FPuIaSZoRFW/Nw 4X0ZPf+ll3iRzDtegehwBIPF4kmc7W13yt+ClxS9bwtWMRzzKJxK7/Kdo5I2Fn4O3Gny 7gL8NdSYliGw3OQoFb32e5LIp9MU/hJjAwvBDon58K6/nAGmdihIuCDQNaOz/XVGsKHt lej/+5iz1SLdISm48/qIvVkM99CMilby6BSs3A5zvYOqc9qRBoxtmPma9CeKK/8NeXsx peYg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b="hGarN/jf"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e7-20020a17090301c700b0016c4f0fc8d3si11109630plh.39.2022.07.13.00.08.29; Wed, 13 Jul 2022 00:08:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b="hGarN/jf"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234501AbiGMHDq (ORCPT + 99 others); Wed, 13 Jul 2022 03:03:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58740 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234495AbiGMHDm (ORCPT ); Wed, 13 Jul 2022 03:03:42 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 222E319022; Wed, 13 Jul 2022 00:03:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=n7mQQpkSKyBeUuYBLyboh7IsO0uahzQ+El0fPXZP7kw=; t=1657695821; x=1658905421; b=hGarN/jfELl75Cyj8v9aaYvKezIHORvfT0kxx2qvArW200S yyOBjQ5pchcQB2863C52jzAsF5Wdf8IDO/4TakWdssBws/sYNmO7sxV92eG4u8JNv0duBT+4icIqV XWj+8KlX3LU2CvUCU9kB07nRKRzW8647uBOC6Nl0NEa9a4uiwRxjrIdjH9yQibVmC63/pC//HcMs7 //EQu7iuiptEKgbIHHL0lqnmc7fsGA5YSaVJqQFBqk0raPpdCE9K4LYX+X9LsY9f4T7XOK5+khQWw 7mHrP4wVP30RDRQhRrjqCTvdk7tY1OP8xflbmohaskJ5FpfdJ3B1+AxB3DMM3EcQ==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.95) (envelope-from ) id 1oBWPD-00Eavy-S1; Wed, 13 Jul 2022 09:03:31 +0200 Message-ID: <9a028efb77ae662fe8eabcf2ffb5a64214f07418.camel@sipsolutions.net> Subject: Re: [PATCH] um: seed rng using host OS rng From: Johannes Berg To: Anton Ivanov , "Jason A. Donenfeld" , linux-um@lists.infradead.org, linux-kernel@vger.kernel.org Cc: stable@vger.kernel.org Date: Wed, 13 Jul 2022 09:03:31 +0200 In-Reply-To: References: <20220712232738.77737-1-Jason@zx2c4.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.3 (3.44.3-1.fc36) MIME-Version: 1.0 X-malware-bazaar: not-scanned X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2022-07-13 at 07:58 +0100, Anton Ivanov wrote: >=20 > IIRC UML RNG device reads directly from host. Yes, but that's a /dev/hwrng device, so you still need some userspace to feed entropy from that into /dev/random. > If you are using UMLs own /dev/random you are effectively using the host= =20 > one. > So unless I am mistaken, you need extra randomness only if you do not=20 > have UMLs /dev/random compiled in. No, neither of those is true. johannes