I've cloned this bug as #898073 and reassigned that to krb5. krb5 is using the new(ish) getrandom() system call to read random bits, with the code comment "This ensures strong randomness while only blocking during first system boot."
While this is a regression, the kernel is only doing what krb5 was asking for (whereas previously it could wrongly provide weak random bits). We might still revert this change in the kernel temporarily. However, the krb5 developers need to decide what they really want, and if that's strong randomness then they need to configure the service to allow for a longer delay at boot. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault.
signature.asc
Description: This is a digitally signed message part
