Re: [PATCH] cpio: code shrink

2022-05-02 Thread Denys Vlasenko
On Thu, Feb 10, 2022 at 2:13 PM Ron Yorston wrote: > Use a generic llist_t to store the names of hardlinked files. > > function old new delta > cpio_o 11401122 -18 > > Signed-off-by: Ron Yorston

Re: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread Bernhard Reutner-Fischer
On 2 May 2022 16:34:25 CEST, Michael Conrad wrote: >On 5/2/22 09:54, Bernhard Reutner-Fischer wrote: >> But why is the seeding being run only at S20, way after udev? > >It needs to be at least late enough for the persistent storage to be mounted, >which probably isn't the root filesystem at

Re: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread Michael Conrad
On 5/2/22 09:54, Bernhard Reutner-Fischer wrote: There is also the case (that on my systems at least) udev initialisation reads from /dev/[u]random well before the S20 script loads any saved entropy. I've not tried to find out what the value is used for. I find at least one occurrence where the

Re: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread Bernhard Reutner-Fischer
On Sun, 1 May 2022 18:35:00 +0200 Emmanuel Deloget wrote: > > There is also the case (that on my systems at least) udev > > initialisation reads from /dev/[u]random well before the S20 > > script loads any saved entropy. > > I've not tried to find out what the value is used for. > > I find at

Re: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread Denys Vlasenko
On Sun, May 1, 2022 at 3:07 PM David Laight wrote: > Using the same file twice is better than having nothing at all. > At least different systems use different values. > Unless you have a remote 'dos' attack that can crash the system > at exactly the right point in the boot sequence this is an >

Re: /sbin/init overrides HOME and TERM env vars

2022-05-02 Thread Denys Vlasenko
On Sat, Mar 12, 2022 at 11:20 AM jkm <8...@wp.pl> wrote: > > Looking at the kernel code in init/main.c, it does look like HOME=/ > > TERM=linux is hard coded in the kernel with no way to override this from > > the command line. > > I guess you are wrong. > HOME and TERM env vars can be overriden

Re: [PATCH] tsort: new applet

2022-05-02 Thread Denys Vlasenko
applied, thank you On Mon, Feb 21, 2022 at 12:59 AM David Leonard wrote: > > Thanks. Patch fixed, attached. > > By the way, is this the right default for config? > > +//config: default n > > David > > On Sun, 20 Feb 2022, tito wrote: > > > some minor fixes inline. > ... > > + /* binry

Re: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread Emmanuel Deloget
Hi, Le lun. 2 mai 2022 à 11:37, Denys Vlasenko a écrit : > > On Mon, May 2, 2022 at 8:26 AM Emmanuel Deloget wrote: > > Le lun. 2 mai 2022 à 03:31, Denys Vlasenko a > > écrit : > > > > I beg to differ, and especially on some embedded systems where the RNG > > > > might be quite controllable

Re: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread Jason A. Donenfeld
On Mon, May 2, 2022 at 11:37 AM Denys Vlasenko wrote: > > On Mon, May 2, 2022 at 8:26 AM Emmanuel Deloget wrote: > > Le lun. 2 mai 2022 à 03:31, Denys Vlasenko a > > écrit : > > > > I beg to differ, and especially on some embedded systems where the RNG > > > > might be quite controllable by an

RE: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread David Laight
From: Alexander Dahl > Sent: 02 May 2022 06:15 > > Am Sat, Apr 30, 2022 at 03:12:11PM +0200 schrieb Denys Vlasenko: > > Do you often pull power cords from machines you use for > > somewhat important crypto operations, such as generating keys? > > What are the chances that you also do it on a

Re: add support for PATH in crontabs

2022-05-02 Thread Denys Vlasenko
Applied, thanks. On Tue, Mar 8, 2022 at 10:13 PM Paul Fox wrote: > > peter0x44 wrote: > > > I'm afraid I can't remember how to generate the cool automatic size > > > diffs. The code change seems to add fewer than 100 bytes, but I also > > > ifdefed a very old level 5 debug loop in

Re: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread Denys Vlasenko
On Mon, May 2, 2022 at 8:26 AM Emmanuel Deloget wrote: > Le lun. 2 mai 2022 à 03:31, Denys Vlasenko a écrit > : > > > I beg to differ, and especially on some embedded systems where the RNG > > > might be quite controllable by an attacker from the outside (mostly > > > because > > > it lacks a

Re: [PATCH v2] seedrng: limit poolsize to 256 bytes and document flock() and fsync() usage

2022-05-02 Thread Emmanuel Deloget
Le lun. 2 mai 2022 à 03:31, Denys Vlasenko a écrit : > > On Sun, May 1, 2022 at 6:35 PM Emmanuel Deloget wrote: > > > > - RNG is seeded and credited using file A. > > > > - File A is unlinked but not fsync()d. > > > > - TLS connection does something and a nonce is generated. > > > > - System