linux-kernel - Re: [PATCH v1 1/1] sysctl: introduce uuid_le and uuid

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 24 May 2016 13:15:08 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:	"Theodore Ts'o" <tytso@....edu>, Arnd Bergmann <arnd@...db.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/1] sysctl: introduce uuid_le and uuid_be

On Tue, 24 May 2016 20:27:27 +0300 Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:

> By default the sysctl interface returns random UUID in big endian format.
> Sometimes it's not suitable, e.g. using generated UUID for EFI variable name.
> Provide uuid_le and uuid_be to comprehence that interface.
> 
> ...
>
>  drivers/char/random.c       | 44 +++++++++++++++++++++++++++++++++++++++++
>  include/uapi/linux/sysctl.h |  4 +++-
>  kernel/sysctl_binary.c      | 48 ++++++++++++++++++++++++++++++++++++++++++++

Why does the kernel need to do this?  If userspace wants a random uuid
then it can grab a random number and cook up the UUID itself.