Date: Thu, 10 Mar 2022 21:21:17 +0000 From: bugzilla-noreply@freebsd.org To: emulation@FreeBSD.org Subject: [Bug 262369] Add /proc/sys/kernel/random/boot_id Message-ID: <bug-262369-4077-T17FeoYVWT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262369-4077@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262369 John Hein <jcfyecrayz@liamekaens.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcfyecrayz@liamekaens.com --- Comment #8 from John Hein <jcfyecrayz@liamekaens.com> --- Note that the linux implementation of these is random, whereas the the freebsd linuxulator implementation is not: for ii in 1 2 3 4 ; do cat /compat/linux/proc/sys/kernel/random/uuid ; done d5491552-a0b6-11ec-a963-90b11c7011ef d5495a75-a0b6-11ec-a963-90b11c7011ef d5497ded-a0b6-11ec-a963-90b11c7011ef d549b78d-a0b6-11ec-a963-90b11c7011ef One might consider this a deficiency or just an idiosyncratic difference between linux and linuxulator. But if it is a deficiency, this is a separate bug. I only made a comment here instead of opening a bug since I'm not sure if I would call it a bug. I guess I lean toward deficiency as the linux random(4) page that documents these files (uuid & boot_id) says "These read-only files contain random strings ...". Maybe it's an open question whether people in the "real world" depend on true randomness for these values. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262369-4077-T17FeoYVWT>