[PATCH] Require minimum random data entropy when creating LUKS (#1073679)

Chris Lumens clumens at redhat.com
Fri Aug 29 21:03:28 UTC 2014


> Creating new LUKS format requires high-quality random data and such quality may
> be specified by minimum entropy of kernel's random data pool required. We can
> tell blivet what should be the minimum entropy available when creating LUKS and
> we can provide callbacks which inform users about what's happening and how they
> can help to increase the available entropy.

From the UI side, we have tried to avoid popups where possible.  I'm not
concerned about the expertness of asking for entropy given that this is
an opt-in thing that people who choose to encrypt will see (and
hopefully they have some idea what entropy means), though perhaps the
wording can be tweaked a little bit.

What I'm more curious about is:  Will we only know there's not enough
entropy when we go to do the encryption, or will we know beforehand?
Would we know at the time the user is entering their passphrase, in
order to combine that task with collecting entropy?  If so, we can avoid
having to do a popup.  If not, I'll have to think about it a little
more.

- Chris


More information about the anaconda-patches mailing list