From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: Stephen Hemminger <stephen@networkplumber.org>,
Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Cc: "Shunzhi Wen" <Shunzhi.Wen@arm.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Ruifeng Wang" <Ruifeng.Wang@arm.com>,
"Bruce Richardson" <bruce.richardson@intel.com>,
"Tyler Retzlaff" <roretzla@linux.microsoft.com>,
"Min Zhou" <zhoumin@loongson.cn>,
"David Christensen" <drc@linux.ibm.com>,
"Stanislaw Kardach" <stanislaw.kardach@gmail.com>,
"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
"Jack Bond-Preston" <Jack.Bond-Preston@arm.com>,
"Dhruv Tripathi" <Dhruv.Tripathi@arm.com>,
"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>
Subject: Re: [PATCH] eal: add support for TRNG with Arm RNG feature
Date: Sun, 28 Jul 2024 08:46:58 +0200 [thread overview]
Message-ID: <6ec424b8-6d3e-414a-8cab-594ef83765e8@lysator.liu.se> (raw)
In-Reply-To: <20240727165524.7ad4f344@hermes.local>
On 2024-07-28 01:55, Stephen Hemminger wrote:
> On Sat, 27 Jul 2024 22:27:05 +0000
> Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com> wrote:
>
>>> The answer is to have API's like (rte_csrand) which then call the OS level
>>> primitives. The trust is then passed to the OS. I trust Linus, Theo de Raadt, and
>>> the rest of the open OS community to evaluate and integrate the best secure
>>> random number generator.
>>
>> Perhaps, you missed my previous email, I understand your concern. Is it acceptable
>> to you if rte_csrand uses the kernel RNG by default and has a build/run-time
>> parameter to switch to HW RNG for those who consciously make that decision?
>
> No, because then DPDK is endorsing use of HW RNG as sole source of randomness.
> If someone really, really wants to do that they can put in their own code
> in their own application.
That's a good point. Even a build-time option (with the required caveats
in the documentation) could be seen as an endorsement.
A DPDK-based security library of some sort could provide hooks for
custom RNGs.
next prev parent reply other threads:[~2024-07-28 7:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 21:27 Shunzhi Wen
2024-07-24 6:40 ` Mattias Rönnblom
2024-07-24 14:35 ` Stephen Hemminger
2024-07-24 15:07 ` Mattias Rönnblom
2024-07-24 16:16 ` Stephen Hemminger
2024-07-24 19:14 ` Mattias Rönnblom
2024-07-24 20:02 ` Stephen Hemminger
2024-07-25 4:48 ` Mattias Rönnblom
2024-07-25 14:56 ` Stephen Hemminger
2024-07-26 18:34 ` Shunzhi Wen
2024-07-26 19:00 ` Stephen Hemminger
2024-07-26 20:12 ` Wathsala Wathawana Vithanage
2024-07-26 22:33 ` Mattias Rönnblom
2024-07-27 15:45 ` Wathsala Wathawana Vithanage
2024-07-27 15:54 ` Stephen Hemminger
2024-07-27 22:27 ` Wathsala Wathawana Vithanage
2024-07-27 23:55 ` Stephen Hemminger
2024-07-28 6:46 ` Mattias Rönnblom [this message]
2024-07-29 4:48 ` Wathsala Wathawana Vithanage
2024-07-27 17:07 ` Mattias Rönnblom
2024-07-27 22:45 ` Wathsala Wathawana Vithanage
2024-07-28 6:42 ` Mattias Rönnblom
2024-07-28 15:52 ` Stephen Hemminger
2024-07-29 4:34 ` Wathsala Wathawana Vithanage
2024-07-29 6:34 ` Wathsala Wathawana Vithanage
2024-07-29 6:47 ` Mattias Rönnblom
2024-07-29 18:16 ` Wathsala Wathawana Vithanage
2024-07-29 18:31 ` Stephen Hemminger
2024-07-29 19:11 ` Mattias Rönnblom
2024-07-29 19:30 ` Morten Brørup
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=6ec424b8-6d3e-414a-8cab-594ef83765e8@lysator.liu.se \
--to=hofors@lysator.liu.se \
--cc=Dhruv.Tripathi@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Jack.Bond-Preston@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=Shunzhi.Wen@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.ibm.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mattias.ronnblom@ericsson.com \
--cc=nd@arm.com \
--cc=roretzla@linux.microsoft.com \
--cc=stanislaw.kardach@gmail.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.com \
--cc=zhoumin@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).