Editing Encryption
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
+ | == Using OS X Core Storage encryption == | ||
− | + | Although upstream OpenZFS has a "project" to work on [http://open-zfs.org/wiki/Projects#Platform_agnostic_encryption_support platform-agnostic encryption support] at the ZFS dataset level, we have an obvious solution to block-level encryption sitting beneath ZFS already at hand: AES-XTS (Core Storage/FileVault 2). | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
This is the OS X analogue of the following block-level encryption systems on other operating systems that support ZFS: | This is the OS X analogue of the following block-level encryption systems on other operating systems that support ZFS: | ||
Line 36: | Line 9: | ||
The overall procedure is, as follows: convert an empty HFS+ partition to use Core Storage and apply Core Storage encryption. Then use the Core Storage Logical Volume as a device in your zpool by supplying it to "zpool create," "zpool add," "zpool attach," etc. | The overall procedure is, as follows: convert an empty HFS+ partition to use Core Storage and apply Core Storage encryption. Then use the Core Storage Logical Volume as a device in your zpool by supplying it to "zpool create," "zpool add," "zpool attach," etc. | ||
− | === | + | === PREREQUISITES === |
Build ZFS [[Install#Installing_from_source|from source]], or wait for the [[Downloads|next installer]], newer than 1.2.0 (for explanation, see original IRC chat). | Build ZFS [[Install#Installing_from_source|from source]], or wait for the [[Downloads|next installer]], newer than 1.2.0 (for explanation, see original IRC chat). | ||
− | === | + | === Caveat === |
− | + | As noted in the article [[suppressing the annoying pop-up]], you will receive a pop-up claiming the disk isn't readable by this computer. | |
+ | This is a well documented problem, see the article above. It does however lead to one step which can be confusing: when decrypting the disk (e.g. on startup), the "bug" will make OSX believe the disk wasn't decrypted, and thus "wiggle" and present the prompt again. | ||
− | + | Take it on faith that once you've decrypted the disk, you can safely close the dialog box (with Cancel). You can verify this with your pools availability. | |
=== Steps === | === Steps === | ||
Line 59: | Line 33: | ||
2: Apple_HFS Internal HD 999.9 GB disk1s2 | 2: Apple_HFS Internal HD 999.9 GB disk1s2 | ||
− | We note that disk1s2 is the partition to be encrypted, and we convert it to | + | We note that disk1s2 is the partition to be encrypted, and we convert it to CoreStorage (think LVM), to enable encryption: |
− | # diskutil | + | # diskutil corestorage convert /dev/disk1s2 |
Started CoreStorage operation on disk1s2 Internal HD | Started CoreStorage operation on disk1s2 Internal HD | ||
Resizing disk to fit Core Storage headers | Resizing disk to fit Core Storage headers | ||
Line 75: | Line 49: | ||
Finished CoreStorage operation on disk1s2 Internal HD | Finished CoreStorage operation on disk1s2 Internal HD | ||
− | Note that we converted the existing unencrypted HFS | + | Note that we converted the existing unencrypted HFS partition. |
Next, we encrypt the logical volume, our Core Storage disk, disk2: | Next, we encrypt the logical volume, our Core Storage disk, disk2: | ||
− | + | # diskutil corestorage encryptVolume /dev/disk2 | |
− | + | ||
− | # diskutil | + | |
New passphrase for existing volume: | New passphrase for existing volume: | ||
Confirm new passphrase: | Confirm new passphrase: | ||
Line 93: | Line 65: | ||
This can and will take a while to complete. You can check the status by issuing: | This can and will take a while to complete. You can check the status by issuing: | ||
− | # diskutil | + | # diskutil cs list | grep "Conversion Progress" |
Until it's done: | Until it's done: | ||
− | |||
Conversion Progress: -none- | Conversion Progress: -none- | ||
Line 117: | Line 88: | ||
0: Apple_HFS *999.5 GB disk2 | 0: Apple_HFS *999.5 GB disk2 | ||
− | disk2 being our encrypted, unlocked HFS | + | disk2 being our encrypted, unlocked HFS device. If you have yet to be prompted for the passphrase by OS X, now would be a good time to restart your Mac and try it out. |
Lastly, we'll prepare the volume for ZFS, by unmounting /dev/disk2: | Lastly, we'll prepare the volume for ZFS, by unmounting /dev/disk2: | ||
Line 124: | Line 95: | ||
... | ... | ||
/dev/disk2 on /Volumes/Internal HD (hfs, local, journaled) | /dev/disk2 on /Volumes/Internal HD (hfs, local, journaled) | ||
− | # | + | # umount "/Volumes/Internal HD" |
− | You can now | + | You can now proceed with [[Zpool#Creating_a_pool]] or standard ZFS manuals. |
− | + | === For illustration purpose === | |
# zpool list | # zpool list | ||
no pools available | no pools available | ||
Line 134: | Line 105: | ||
# zpool list | # zpool list | ||
ZFS_VOLUME 928G 20.8G 907G 2% 1.00x ONLINE - | ZFS_VOLUME 928G 20.8G 907G 2% 1.00x ONLINE - | ||
− | |||
− | |||
− | + | ||
− | + | == Reason for "use latest" == | |
− | < | + | This commit is potentially vital: |
− | < | + | e795742 ilovezfs: Make the check for Core Storage LV more forgiving. |
− | <lundman> :) | + | |
− | < | + | === Original IRC chat === |
− | < | + | [14:07] < ilovezfs_> if you want encryption you have a few options |
− | < | + | [14:07] < ilovezfs_> https://github.com/zfsrogue/osx-zfs-crypto |
− | + | [14:07] < lundman> :) | |
− | < | + | [14:08] < ilovezfs_> or you can do what cbreak-work said, and use an encrypted sparsebundle |
− | < | + | [14:08] < ilovezfs_> (I'd give it its own zfs file system) |
− | < | + | [14:08] < ilovezfs_> or you can create a zvol, and put an encrypted CoreStorage/Filevault2 HFS+ file system on it |
− | < | + | [14:09] < ilovezfs_> or you can put the pool itself on top of CoreStorage |
− | <aandy> | + | [14:09] < ilovezfs_> The last option you should not do with the installer version. |
− | < | + | [14:10] < ilovezfs_> But wait for the next installer if that's the route you want to go |
− | < | + | [14:10] < ilovezfs_> or build from source. |
− | < | + | [14:10] < aandy> ah, interesting. does filevault2 require hfs+? not that it'd surprise me |
− | < | + | [14:11] < ilovezfs_> no it does not |
− | < | + | [14:11] < ilovezfs_> but it is not possible to set other Content Hints |
− | < | + | [14:11] < ilovezfs_> so it will always say HFS+ even if you do put ZFS on your logical volumes |
− | < | + | - |
− | < | + | [14:13] < ilovezfs_> aandy: so basically the procedure is to format the volume HFS+ |
− | < | + | [14:13] *** ottmarklaas [~ottmarkla@cpe-67-248-51-197.nycap.res.rr.com] has quit [Quit: ottmarklaas] |
− | <aandy> | + | [14:13] < ilovezfs_> aandy: then run 'diskutil corestorage convert' on it |
− | < | + | [14:13] < ilovezfs_> then you can encrypt it |
− | < | + | [14:14] < ilovezfs_> then you unmount the HFS+ |
− | < | + | [14:14] < ilovezfs_> and zpool create on the logical volume. |
− | <aandy> | + | [14:14] < ilovezfs_> And you should be good to go. |
− | < | + | [14:14] < aandy> on the original HFS+ partition, right? |
− | < | + | [14:14] < ilovezfs_> right |
− | < | + | [14:14] < ilovezfs_> but id encrypt first |
− | < | + | [14:14] < ilovezfs_> then put zfs on |
− | + | [14:14] < aandy> right. perfect | |
− | < | + | [14:15] < ilovezfs_> diskutil cs convert... |
− | < | + | [14:15] < ilovezfs_> diskutil cs encryptVolume ... |
− | + | [14:15] < ilovezfs_> etc. | |
− | + | [14:16] < ilovezfs_> The reason not to use the installer version, is that it will attempt to partition the Core Storage Logical Volume. | |
+ | [14:16] < ilovezfs_> But since 10.8.5 and after, Apple doesn't like that. | ||
+ | [14:16] < ilovezfs_> So we added new code to detect Core Storage and not partition if it sees it's Core Storage. | ||
+ | |||
+ | == Time Machine Backups == | ||
+ | As a follow-up, here's one approach to using ZFS for your Time Machine Backups: | ||
+ | |||
+ | While it has been discussed in heated arguments, e.g. https://github.com/openzfsonosx/zfs/issues/66, I still believe there's at least one ZFS feature I'd like to test with Time Machine: compression. | ||
+ | |||
+ | The hypothesis being: | ||
+ | a HFS+ sparse bundle stored on a compressed (gzip, lz4), deduped dataset should | ||
+ | yield a compression ratio > 1.0. | ||
+ | (previously observed 1.4 with compression=on, dedup=off, FreeBSD network Time Machine drives). | ||
+ | |||
+ | To work around compatible disks for Time Machine, we create a HFS+ bundle, store it on ZFS and set the mounted image as a backup destination, no "TMShowUnsupportedNetworkVolumes" needed. | ||
+ | |||
+ | 1. Create, and mount, a sparse bundle from your zfs filesystem, e.g. with makeImage.sh | ||
+ | |||
+ | 2. Set your sparse bundle as the (active) backup destination # tmutil setdestination -a /Volumes/Time\ Machine\ Backups |