Due to the limitations, you might want to use an encrypted disk image rather than whole disk encryption.
Come to think of it - why not use both?
You could always turn off FileVault if you felt it too much a hassle, but to get around the limitation you caught (thank goodness you did catch it), consider using Disk Utility to make secure the parts of your data you need to force into a locked state when that disk image is unmounted. This will let you sleep your mac and not compromise that data by allowing it to be re-mounted without the appropriate passcode being supplied.
No, sorry chickpee, I believe you're incorrect.
Is an encrypted Time Machine disk really just the same as a normal
disk, full-disk-encrypted using FileVault?
Yes. It is. This would be "FileVault 2" we are talking about, aka CoreStorage, Apple's newish logical volume manager. This is different that the previous TM and FileVault technologies, which are based on AES-encrypted sparse-bundle disk images (which are still used for network backups, etc.). The process that starts in System Preferences (these days) when you enable disk encryption (whether on an external disk, for Time Machine, or on the boot drive for FileVault), provided the disk is suitable, it does an online conversion from a traditional GPT Partition Table to a single monolithic data store, with a very small partition for the CS firmware. Logical volumes (in logical volume groups) are then carved out of this, and these (software) volumes are then HFS formatted and encrypted.
I believe the most straightforward method for doing this would be to:
- Attach the disk you're going to use, wipe it. Free space or a single HFS+ partition.
diskutil cs create/convert (wasn't/was formatted; unimportant) to initialize and add a new LVGdiskutil cs createVolume, create a single LV. You could enable encryption at this point, with diskutil cs encryptVolume, if you know the passphrase you're going to use;
if not, leave it unencrypted for now.diskutil partitionDisk diskX -- see below -- CS volumes appear as if they are completely autonomous, separate disks, so you partitionDisk.
Then: mount and unlock the volume on your new user's machine. Once the disk is unlocked, there shouldn't be any trouble 'adopting' it for use there. If you want to put it into a config script, I believe it's just something like tmutil -a /Volumes/Foo, tmutil startbackup -ad disk.... This is the part I'm least sure about, but I'm also sure its easily doable. I haven't done this for Time Machine per se my self, but I pre-encrypt disks for FileVault like this all the time, and the OS sort of just knows what to do with if after that.
A properly suitable CS-enabled-disk is going to appear like this in diskutil (although you might not have the third partition on disk0 if it's knows it's not going to be a boot drive:
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage 250.1 GB disk0s2
3: Apple_Boot Boot OS X 250.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh LV *249.8 GB disk1
disk0 will not appear as encrypted, ever, since this is what the volume manager basically has to 'boot' off of. disk1 will be encrypted and will require the passcode to mount.
Best Answer
Filevault's use the XTS-AES 128 encryption. As Finder's contextual menu encryptation option and the Erase with the Encrypted format use Filevault's system, the encryption is the same.
Disk Utility's, in the other hand, when creating an new image, lets you choose between a 128 or 256 bits AES Encryption.
These two methods are, therefore, different. The latter just creates a folder which requires a password to be opened, while Filevault is a lot more complex.
And for the Logical Partition, here is explained in detail.