Re:Problems emerge for a unified /dev/*random
by yxhuvud on Wednesday March 30, 2022 @12:33AM
(#30851507)
Also,the problems seems mostly to be around Linux running in a VM rather than on actual hardware. Would it be possible to have the host urandom show up as a hw random number generator to the VM and then use that for initiating things? Seems less hacky than having to fiddle with seeds. Dunno how possible that is though.
[ Parent
| on HN ]
Re:Problems emerge for a unified /dev/*random
by pm215 on Wednesday March 30, 2022 @05:53AM
(#30853198)
You can do that where for instance the VM has PCI and can plug in a virtio RNG device. But a lot of the QEMU setups Guenter Roeck reported issues with are emulating real (usually old) hardware which didn't have a PCI bus, or any other hardware RNG interface.
Re:Problems emerge for a unified /dev/*random
by mjevans on Wednesday March 30, 2022 @06:19AM
(#30853340)
Also lighter systems such as routers (E.G. many OpenWRT targets)
Re:Problems emerge for a unified /dev/*random
by AnssiH on Wednesday March 30, 2022 @05:18AM
(#30852978)
Yes, and that is commonly used.
But Linux must continue to work even on VMs without that, and that is the hard part.
Re:Problems emerge for a unified /dev/*random
by loeg on Wednesday March 30, 2022 @10:46AM
(#30855935)
The VMs described in the article are (faithfully) emulating real hardware lacking unpredictable timers or other sources of entropy. It’s not exclusively a VM problem; it’s a weird/old hardware problem, too.