public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] lib: uuid: Improve randomness of uuid values on RANDOM_UUID=y
Date: Sat, 27 Apr 2019 17:05:28 +0200	[thread overview]
Message-ID: <20190427170528.5a6f4576@jawa> (raw)
In-Reply-To: <20190426215458.5057-1-erosca@de.adit-jv.com>

On Fri, 26 Apr 2019 23:54:58 +0200
Eugeniu Rosca <roscaeugeniu@gmail.com> wrote:

> The random uuid values (enabled via CONFIG_RANDOM_UUID=y) on our
> platform are always the same. Below is consistent on each cold boot:
> 
>  => ### reach U-Boot prompt
>  => setenv uuid_gpt_misc
>  => gpt verify mmc 1 $partitions  
>     Verify GPT: success!
>  => print uuid_gpt_misc  
>     uuid_gpt_misc=d117f98e-6f2c-d04b-a5b2-331a19f91cb2
>  => setenv uuid_gpt_misc
>  => gpt verify mmc 1 $partitions  
>     Verify GPT: success!
>  => print uuid_gpt_misc  
>     uuid_gpt_misc=ad5ec4b6-2d9f-8544-9417-fe3bd1c9b1b3
> 
> While the uuids do change on every 'gpt {write,verify}' command,
> the values appear to be taken from the same pool, in the same order.
> 
> As a user, I expect a trully random uuid value in the above example.
> Otherwise, system/RFS designers and OS people might assume they have
> a reliable/consistent uuid passed by the bootloader, while the truth
> is U-Boot simply lacks entropy to generate a random string.
> 
> Let's use get_timer() to update the seed, same as done in commit
> da384a9d7628 ("net: rename and refactor eth_rand_ethaddr() function").
> 
> Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
> ---
>  lib/uuid.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/lib/uuid.c b/lib/uuid.c
> index fa20ee39fc32..8a82cb234b88 100644
> --- a/lib/uuid.c
> +++ b/lib/uuid.c
> @@ -238,6 +238,8 @@ void gen_rand_uuid(unsigned char *uuid_bin)
>  	unsigned int *ptr = (unsigned int *)&uuid;
>  	int i;
>  
> +	srand(get_timer(0));
> +
>  	/* Set all fields randomly */
>  	for (i = 0; i < sizeof(struct uuid) / sizeof(*ptr); i++)
>  		*(ptr + i) = cpu_to_be32(rand());

Reviewed-by: Lukasz Majewski <lukma@denx.de>


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190427/23d82eb0/attachment.sig>

  reply	other threads:[~2019-04-27 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 21:54 [U-Boot] [PATCH] lib: uuid: Improve randomness of uuid values on RANDOM_UUID=y Eugeniu Rosca
2019-04-27 15:05 ` Lukasz Majewski [this message]
2019-04-29 10:00   ` Eugeniu Rosca
2019-04-29 13:00   ` Eugeniu Rosca
2019-04-30  3:04     ` Eugeniu Rosca

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190427170528.5a6f4576@jawa \
    --to=lukma@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox