From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 4/4] ndp: Use high quality entropy in NDP timer even if not needed
Date: Thu, 16 Jul 2026 17:34:25 +1000 [thread overview]
Message-ID: <aliJdtb4JjZBE7YH@zatzit> (raw)
In-Reply-To: <20260716072222.1819811-5-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]
On Thu, Jul 16, 2026 at 09:22:22AM +0200, Stefano Brivio wrote:
> ...instead of calling random(), to make static checkers happy.
>
> I don't think that an attacker could actually gain anything by making
> router advertisement intervals predictable, but a doubt remains, and
> this is cheap enough that we might just want to do this to get rid of
> the noise from static checkers informing us that random() shouldn't be
> used.
>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> v2: Turn random_part to uint32_t and cast to time_t before using it, to
> avoid using negative values
>
> ndp.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/ndp.c b/ndp.c
> index 1f2bcb0..439fc0c 100644
> --- a/ndp.c
> +++ b/ndp.c
> @@ -413,6 +413,7 @@ void ndp_timer(const struct ctx *c, const struct timespec *now)
> {
> time_t max_rtr_adv_interval = DEFAULT_MAX_RTR_ADV_INTERVAL;
> time_t min_rtr_adv_interval, interval;
> + uint32_t random_part;
>
> if (!tap_is_ready(c) || c->no_ra || now->tv_sec < next_ra)
> return;
> @@ -433,15 +434,18 @@ void ndp_timer(const struct ctx *c, const struct timespec *now)
> * and causing flurries of RAs at the same time.
> *
> * This random doesn't need to be cryptographically strong, so random(3)
> - * is fine. Other routers on the link also want to avoid
> - * synchronisation, and anything malicious has much easier ways to cause
> - * trouble.
> + * would be fine. Other routers on the link also want to avoid
> + * synchronisation, and anything malicious would have much easier ways
> + * to cause trouble. However, for the sake of static checkers, use high
> + * quality entropy as provided by raw_random().
> *
> * The modulus also makes this not strictly a uniform distribution, but,
> * again, it's close enough for our purposes.
> */
> + raw_random(&random_part, sizeof(random_part));
> interval = min_rtr_adv_interval +
> - random() % (max_rtr_adv_interval - min_rtr_adv_interval);
> + (time_t)random_part % (max_rtr_adv_interval -
> + min_rtr_adv_interval);
>
> if (!next_ra)
> goto first;
> --
> 2.43.0
>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-16 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 7:22 [PATCH v2 0/4] Assorted fixes, address a static checker warning Stefano Brivio
2026-07-16 7:22 ` [PATCH v2 1/4] CONTRIBUTING.md: The tag is "Link:", regardless of how many we have Stefano Brivio
2026-07-16 7:22 ` [PATCH v2 2/4] dhcp: Make option parsing more robust, explicitly handle options 0 and 255 Stefano Brivio
2026-07-16 7:30 ` David Gibson
2026-07-16 7:22 ` [PATCH v2 3/4] passt.1, pesto.1: ::1 is an address, not a port Stefano Brivio
2026-07-16 7:22 ` [PATCH v2 4/4] ndp: Use high quality entropy in NDP timer even if not needed Stefano Brivio
2026-07-16 7:34 ` David Gibson [this message]
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=aliJdtb4JjZBE7YH@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).