| Solaris |
|
|
Encryption is the process where data is encoded for privacy and a key is needed by the data owner to access the encoded data.
See Darren's blog that briefly describes ZFS encryption in the Oracle Solaris 11 Express release.
You can encrypt a ZFS file system when it is created by setting the encryption property to on.
# zfs create -o encryption=on tank/home/darren
No, encryption can only be enabled or disabled at creation time. This policy ensures that all the data in a ZFS file system or volume is always encrypted. This feature is very important because ZFS is copy-on-write and does not overwrite data that is in place.
Yes, the pool must be upgraded to pool version 30 to allow encrypted ZFS file systems and volumes.
Not at this time, but this feature is being considered. You can use the cp -r, find | cpio, tar, or rync commands to migrate unencrypted file system data to a file system with encryption enabled.
Yes, if the properties are NOT sent by using the zfs send -p option and this is not a replication stream by using the zfs send -R option, then this operation is allowed.
No.
Yes, you can enable compression and deduplication on an encrypted file system. For descendent file systems, such as clones, data will be deduped provided that the zfs key -K or zfs clone -K operations, which change the data encryption keys, have not be used on the clone file systems.
Yes. A PAM module to assist with encrypting users' home directories is being considered
Terms of Use
|
Privacy
|
Trademarks
|
Copyright Policy
|
Site Guidelines
|
Site Map
|
Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
© 2012, Oracle Corporation and/or its affiliates.