Yes. As I said, the current implementation fails to live up to the distinction.<p>They should be completely partitioned pools, and collected entropy that goes out random should never be mixed into the urandom pool. Of course it&#x27;s likely random still wants whitening, likely resulting in the use of a computationally-secure algorithm.<p>Practically since it&#x27;s anyone&#x27;s guess what the random clients expect, it&#x27;s probably the right thing to `ln -f urandom random`. Bona fide hardware sources can come up with their own device&#x2F;daemon to administer and&#x2F;or stir into the kernel P&#x2F;RNG. I&#x27;m just pointing out that there is a worthwhile distinction they were trying for, despite the engineering pitfalls of trying to make it available!