On Tue, 10 Feb 2026 at 19:28, Roberto A. Foglietta <[email protected]> wrote: > > On Tue, 27 Jan 2026 at 23:57, Roberto A. Foglietta > <[email protected]> wrote: > > > > On Mon, 26 Jan 2026 at 15:04, Roberto A. Foglietta > > <[email protected]> wrote: > > > > > [...] > > > ~> https://github.com/robang74/working-in-progress/blob/main/random.txt > > > > Sure it was broken, the generation of the random numbers via shell... > > ...and when something is SO broken, it is impossible to fix, right? > > > > Fixed. > > Also with a single process in userspace and fixed text as input > > https://github.com/robang74/working-in-progress/blob/eba0a10e1509df224398564bf8a50b013c19a0a7/prpr/uchaos.c >
Confirmed and 3rd party testable About random generators: uChaos testing in 0°K VM in: 1. blms-v0.2.5, 2. run sh start.sh -Z or -z for manual - https://github.com/robang74/working-in-progress/blob/main/README.md the 0°K VM is a "marketing" (or just for fun) way to refer to a qemu VM running an almost allnoconfig kernel with no devices aparte the strictly necessary, software tgc emulation with debug config about -icount strongly deterministic as usually debugging requires. These VMs usually lack entropy and when almost isolated (serial apart) are hard to seed as well (1 cpu, !SMP, 1 single userland process). Despite this, uchaos manage to extract and use for creating good (enough?) randomness quickly or in large quantities (per unit of time). The code is portable in terms of system calls on other arch than x86 and potentially also into the kernel space. - https://github.com/robang74/bare-minimal-linux-system/releases/tag/bmls-v0.2.5 The two links above are about project presentation and automatic system testing in VMs by PractRand musl static. Instead, here below the page that in a "wonderful land manner" describes the principle behind that chaos shows to be solid (apparently, everything is debatable forever). - https://github.com/robang74/working-in-progress/blob/main/uchaos-vs-thermodynamics.md#the-stochastics-hits-creates-ripples-2%E2%81%BF-fading The rationale is simple: a 100% software VM and the scheduler can provide entropy like if they were a small sample of matter coupled with an over-precise thermometer outside the controlled environment of a scientific laboratory. If (and I am underlingin IF) uchaos shows that real-entropy exists not because matter/energy but everywhere information is present/available then it is because I refused to use any cryptographic means. Thus nothing inside uchaos.c code that can "simulate" entropy or white noise. I am not sure that jitterentropy made this step further, aka put the proj itself as a PoC of a physical principle aka entropy is information and "without a structure" is not even an absolute characteristic. Or said in different wordings, entropy and information are the same thing apart from our ability to understand information and nothing about entropy. Which also means that security is about predictability (cost) from the attackers' side. Please take this e-mail as an invitation to collaborate or contribute to the project. Including its possible integration in busybox. Best regards, -- Roberto A. Foglietta +49.176.274.75.661 +39.349.33.30.697 _______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox
