Comment 27 for bug 2064909

So I came across this bug because I was *trying* to use a separate unencrypted boot partition, but then calamares yelled at me with:

A separate boot partition was set up together with an encrypted root partition, but the boot partition is not encrypted.

There are security concerns with this kind of setup, because important system files are kept on an unencrypted partition.
You may continue if you wish, but filesystem unlocking will happen later during system startup.
To encrypt the boot partition, go back and recreate it, selecting Encrypt in the partition creation window.

My understanding from previous versions of Ubuntu that /boot needed to be unencrypted, so I was a little surprised when the installer bugged me to encrypt it. Since this apparently isn't actually properly possible, can it be fixed to *not* tell me to do something I shouldn't do?