Not a bug. My fault.
Manually encrypting the devices in the shell requires the use of "fdisk"
to create 2 partitions, one FAT32 (0C) and the other OpenBSD (A6). By
calling "fdisk -iy", it would only create one A6 partition. The
Raspberry Pi will not boot like this.
Only the guided installation was working before (with a passphrase) --
it creates the 2 partitions for you. I never actually attempted to
manually encrypt the devices in a shell, with a passphrase, or it would
also fail -- and this bug report would never have existed. Sorry.
I tried to mirror what the guided installation creates: a 16MB (32768)
Win95 FAT32L partition number 0 (starting at 32768), and an OpenBSD
partition number 3 starting at 65536, taking up the rest of the disk. It
worked. A fully-encrypted Raspberry Pi. Wonderful.
