Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750993AbdHQE4T (ORCPT ); Thu, 17 Aug 2017 00:56:19 -0400 Received: from mail-wr0-f182.google.com ([209.85.128.182]:33712 "EHLO mail-wr0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750738AbdHQE4S (ORCPT ); Thu, 17 Aug 2017 00:56:18 -0400 MIME-Version: 1.0 In-Reply-To: <20170816224650.1089-3-labbott@redhat.com> References: <20170816224650.1089-1-labbott@redhat.com> <20170816224650.1089-3-labbott@redhat.com> From: Nick Kralevich Date: Wed, 16 Aug 2017 21:56:15 -0700 Message-ID: Subject: Re: [kernel-hardening] [PATCHv2 2/2] extract early boot entropy from the passed cmdline To: Laura Abbott Cc: Kees Cook , Daniel Micay , kernel-hardening@lists.openwall.com, lkml , linux-mm@kvack.org, Andrew Morton Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 582 Lines: 14 On Wed, Aug 16, 2017 at 3:46 PM, Laura Abbott wrote: > From: Daniel Micay > > Existing Android bootloaders usually pass data useful as early entropy > on the kernel command-line. It may also be the case on other embedded > systems. Sample command-line from a Google Pixel running CopperheadOS: > Why is it better to put this into the kernel, rather than just rely on the existing userspace functionality which does exactly the same thing? This is what Android already does today: https://android-review.googlesource.com/198113 -- Nick