linux-kernel - Re: [PATCH 3/3] vsprintf: Add use-early-random-bytes cmd line option

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 2 May 2018 14:56:45 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     "Tobin C. Harding" <me@...in.cc>
Cc:     linux-kernel@...r.kernel.org,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Randy Dunlap <rdunlap@...radead.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Kees Cook <keescook@...omium.org>,
        Anna-Maria Gleixner <anna-maria@...utronix.de>,
        "Theodore Ts'o" <tytso@....edu>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH 3/3] vsprintf: Add use-early-random-bytes cmd line
 option

On Wed,  2 May 2018 09:33:40 +1000 "Tobin C. Harding" <me@...in.cc> wrote:

> Currently if an attempt is made to print a pointer before there is
> enough entropy then '(____ptrval____)' is printed.  This makes debugging
> early stage stack traces difficult.  We can relax the requirement for
> cryptographically secure hashing when debugging while still maintaining
> pointer hashing behaviour.
> 
> Add a command line option 'use-early-random-bytes'.  When enabled get
> key material from the hw RNG if available.

Documentation/admin-guide/kernel-parameters.rst, please.

> This option should NOT be enabled on production kernels.

And the documentation should explain why this recommendation is made. 
Here was I scratching my head wondering why this feature isn't just
permanently enabled.  Still scratching away...