linux-kernel - Re: [PATCH] lib: fix three typos in Kconfig help text

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] [day] [month] [year] [list]

Message-ID: <f6a5b93b-ea49-0c95-0702-152aba7ea48a@infradead.org>
Date:   Thu, 30 Aug 2018 12:52:12 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Thibaut Sautereau <thibaut@...tereau.fr>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     Ingo Molnar <mingo@...nel.org>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Arnd Bergmann <arnd@...db.de>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Waiman Long <longman@...hat.com>,
        Mikulas Patocka <mpatocka@...hat.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lib: fix three typos in Kconfig help text

On 08/30/2018 12:45 PM, Thibaut Sautereau wrote:
> Fix three typos in CONFIG_WARN_ALL_UNSEEDED_RANDOM help text.
> 
> Signed-off-by: Thibaut Sautereau <thibaut@...tereau.fr>

Acked-by: Randy Dunlap <rdunlap@...radead.org>

Thanks.

> ---
>  lib/Kconfig.debug | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index c7fef0c56d6b..3e50cc93572c 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1277,13 +1277,13 @@ config WARN_ALL_UNSEEDED_RANDOM
>  	  time.  This is really bad from a security perspective, and
>  	  so architecture maintainers really need to do what they can
>  	  to get the CRNG seeded sooner after the system is booted.
> -	  However, since users can not do anything actionble to
> +	  However, since users cannot do anything actionable to
>  	  address this, by default the kernel will issue only a single
>  	  warning for the first use of unseeded randomness.
>  
>  	  Say Y here if you want to receive warnings for all uses of
>  	  unseeded randomness.  This will be of use primarily for
> -	  those developers interersted in improving the security of
> +	  those developers interested in improving the security of
>  	  Linux kernels running on their architecture (or
>  	  subarchitecture).
>  
> 


-- 
~Randy