The policy questions are only very distantly tangential to the topic of this report.
The point is, no matter what policy is adopted, there needs to be a way to *implement* the policy. There needs to be some concrete *command* to put into the cron entry or whatever. The logical, systematic, traditional, and expected command to use for this would be "systemctl start systemd-random-seed" or the equivalent. I am quite aware that dd(1) or write(2) could be used to achieve the same result, but that would require duplication of code and duplication of effort. There is a smallish but nonzero amount of logic that the code needs to implement. The difficulties are exacerbated by the incompatible locations /var/lib/urandom/random-seed and /var/lib/systemd/random-seed So the point remains: There ought to be a nice standard systematic structured method for carrying out whatever policy is adopted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652381 Title: systematic way to refresh the random-seed again and again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1652381/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
