The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "Michael Kjörling" <e5655f30a07f@ewoof.net>, tuhs@tuhs.org
Subject: [TUHS] Re: Unix install & "standalone" package
Date: Tue, 12 Sep 2023 00:05:47 +0200	[thread overview]
Message-ID: <20230911220547.atSg7%steffen@sdaoden.eu> (raw)
In-Reply-To: <20230911041059.GH701295@mit.edu>

Theodore Ts'o wrote in
 <20230911041059.GH701295@mit.edu>:
 |On Sat, Sep 09, 2023 at 01:38:54AM +0200, Steffen Nurpmeso wrote:
 |> You know, things change, and if you do not follow closely, you
 |> stand in the rain.  I am not a paid Linux engineer that follows
 |> this rapidly moving target in the end.
 |> For example the (no longer) new random developer chose to disable
 |> feeding entropy via /dev/urandom, here (distribution) still is
 |> 
 |>   # Load random seed
 |>   /bin/cat /var/lib/urandom/seed > /dev/urandom
 |> 
 |> for almost two decades (it is a rather young one), but the code
 |> path was mutilated (i read the kernel source once he had rewritten
 |> that to be blake2/some 32-byte block thing based), now one needs
 |> to use some ioctl interface fwiw.
 |
 |Huh?  That's not correct.  You can still introduce entropy into the
 |random pool by writing to /dev/urandom or /dev/random.  It is true
 |that there has been some changes to the design of /dev/random, but I
 |assure you as the original /dev/random developer, was consulted and
 |involved in the design discussions.

Ah, lesser and lesser freedom for man!  That is the truth!
Neither was (last i looked) that counted no more to unlock man
from the chokehold of missing entropy, nor do newer kernels then
decrement entropy when you read random.

 |Anyway, this is off-topic for TUHS, but if you have specific
 |questions/complaints, feel free to address them to me and Jason.  Your
 |comments do make me suspect that there are some fundamental
 |misunderstandings at work.

Surely for the latter.  So much i give in on this song line.

Greetings.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

  reply	other threads:[~2023-09-11 22:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 14:44 [TUHS] " Norman Wilson
2023-09-04 14:55 ` [TUHS] " Vincenzo Nicosia
2023-09-04 17:20   ` Warner Losh
2023-09-04 19:05     ` Clem Cole
2023-09-05 17:03       ` Paul Winalski
2023-09-05 18:02         ` Clem Cole
2023-09-04 19:59     ` Theodore Ts'o
2023-09-04 23:51       ` Warner Losh
2023-09-04 17:18 ` Warner Losh
2023-09-04 22:10 ` Steffen Nurpmeso
2023-09-05 15:53   ` Steffen Nurpmeso
2023-09-06 17:50     ` Warner Losh
2023-09-07  0:11       ` Steffen Nurpmeso
2023-09-07 16:05         ` Warner Losh
2023-09-08 14:58           ` Theodore Ts'o
2023-09-08 13:56     ` Michael Kjörling
2023-09-08 23:38       ` Steffen Nurpmeso
2023-09-09 22:43         ` Steffen Nurpmeso
2023-09-11  4:10         ` Theodore Ts'o
2023-09-11 22:05           ` Steffen Nurpmeso [this message]
2023-09-05  1:07 ` Jonathan Gray
  -- strict thread matches above, loose matches on Subject: below --
2023-09-04  9:57 [TUHS] " Paul Ruizendaal via TUHS
2023-09-04 14:53 ` [TUHS] " emanuel stiebler
2023-09-04 17:07 ` Warner Losh
2023-09-04 18:21   ` Dan Cross
2023-09-05 11:15   ` Paul Ruizendaal via TUHS
2023-09-05 14:15     ` Clem Cole
2023-09-05 17:03     ` Warner Losh

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=20230911220547.atSg7%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=e5655f30a07f@ewoof.net \
    --cc=tuhs@tuhs.org \
    --cc=tytso@mit.edu \
    /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).