On Thu, 23 May 2024 12:49:50 +0800
Herbert Xu wrote:
> On Wed, May 22, 2024 at 03:53:23PM -0700, Linus Torvalds wrote:
> >
> > That said, looking at the code in question, there are other oddities
> > going on. Even the "we found a favorite new rng" case looks rather
> > strange. The thread we us
On Fri, 18 Dec 2020 10:25:19 -0300
Marcelo Henrique Cerri wrote:
> Hi, Ted and Jason.
>
> Any updates on that?
>
> I don't believe Torsten's concerns are simply about *applying* patches
> but more about these long periods of radio silence. That kills
Exactly. I could live with replies in the s
Hi Linus!
AFAIK it's legit to bother you directly with issues like this one?
I see certifications as the mere messengers here which tell us that
our /dev/random is technologically outdated. Input entropy amounts are
guesstimated in advance, obviously much too conservatively, compiled in
and never
On Mon, Nov 02, 2020 at 02:44:35PM +0100, Torsten Duwe wrote:
>
> Ted, if you don't have the time any more to take care of /dev/random,
> it's not a shame to hand over maintainership, especially given your
> long history of Linux contributions.
>
> Please do seriously
On Wed, 28 Oct 2020 19:07:28 +0100
Greg Kroah-Hartman wrote:
> On Wed, Oct 28, 2020 at 06:51:17PM +0100, Torsten Duwe wrote:
> > On Mon, 19 Oct 2020 21:28:50 +0200
> > Stephan Müller wrote:
> > [...]
> > > * Sole use of crypto for data processing:
> > [...]
On Mon, 19 Oct 2020 21:28:50 +0200
Stephan Müller wrote:
[...]
> * Sole use of crypto for data processing:
[...]
> - The LRNG uses only properly defined and implemented cryptographic
>algorithms unlike the use of the SHA-1 transformation in the
> existing /dev/random implementation.
>
> - H
On Fri, Oct 02, 2020 at 03:56:28PM +0200, Stephan Mueller wrote:
> Am Freitag, 2. Oktober 2020, 15:15:55 CEST schrieb Willy Tarreau:
>
> Hi Willy,
>
> > > And this is all ???
> >
> > Possibly a lot of people got used to seeing the numerous versions
> > and are less attentive to new series, it's
On Fri, Oct 02, 2020 at 03:33:58PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Oct 02, 2020 at 03:15:55PM +0200, Willy Tarreau wrote:
> > On Fri, Oct 02, 2020 at 02:38:36PM +0200, Torsten Duwe wrote:
> > > Almost two weeks passed and these are the "relevant" replies:
&
Almost two weeks passed and these are the "relevant" replies:
Jason personally does not like FIPS, and is afraid of
"subpar crypto". Albeit this patch set strictly isn't about
crypto at all; the crypto subsystem is in the unlucky position
to just depend on a good entropy source.
Greg claims that
On Tue, 22 Sep 2020 18:21:52 +0200
Greg Kroah-Hartman wrote:
> On Tue, Sep 22, 2020 at 03:23:44PM +0200, Torsten Duwe wrote:
> > On Mon, Sep 21, 2020 at 10:40:37AM +0200, Stephan Mueller wrote:
> > > Am Montag, 21. September 2020, 09:58:16 CEST schrieb Ni
On Mon, Sep 21, 2020 at 10:40:37AM +0200, Stephan Mueller wrote:
> Am Montag, 21. September 2020, 09:58:16 CEST schrieb Nicolai Stange:
>
> > - people dislike the approach of having two competing implementations for
> > what is basically the same functionality in the kernel.
>
> Is this really
On Thu, Aug 30, 2018 at 11:00:14AM -0400, Martin K. Petersen wrote:
> Introduce a facility that can be used to receive a notification
> callback when a new algorithm becomes available. This can be used by
> existing crypto registrations to trigger a switch from a software-only
> algorithm to a hard
On Tue, Jun 20, 2017 at 10:21:17PM +0800, Sean Wang wrote:
> Hi Herbert,
>
> thanks for effort reviewing on those patches.
>
> By the way, also loop in Torsten
>
> Could you kindly guide me how to determine appropriate
> rng->ops.quality value used by the driver?
>
> I have tested with rngtest
13 matches
Mail list logo
