Public bug reported: Started in a discussion at [1] And eventually finalized in [2] and a commit at [3]
We need to avoid systems hanging due to the long delay on start especially with kernel >=4.17 IIRC. Since this will soon be released with Cosmic and HWE Kernels for Bionic we don't want cloud instances to suddenly initialize much slower. TL;DR: The fallback always was to urandom, it just got a new case to do so, which is not being able to deliver enough entropy. Since this has a rather low but potential security drawback [2] I also will ping the security people to check and [n]ack this. [1]: https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-users/2018/04/msg00036.html [2]: https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-users/2018/05/msg00060.html [3]: https://git.tuxfamily.org/chrony/chrony.git/commit/?id=7c5bd948bb7e21fa0ee22f29e97748b2d0360319 ** Affects: chrony (Ubuntu) Importance: Medium Status: Triaged ** Affects: chrony (Ubuntu Bionic) Importance: Medium Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787366 Title: avoid service start hang due to random changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1787366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
