Issues Fixed in Cloudera Navigator Encrypt
The following sections describe issues fixed in each Cloudera Navigator Encrypt release.
- Issues Fixed in Cloudera Navigator Encrypt 3.16.0
- Issues Fixed in Cloudera Navigator Encrypt 3.15.0
- Issues Fixed in Cloudera Navigator Encrypt 3.14.0
- Issues Fixed in Cloudera Navigator Encrypt 3.13.0
- Issues Fixed in Cloudera Navigator Encrypt 3.12.2
- Issues Fixed in Cloudera Navigator Encrypt 3.12.0
- Issues Fixed in Cloudera Navigator Encrypt 3.11.0
- Issues Fixed in Cloudera Navigator Encrypt 3.10.0
- Issues Fixed in Cloudera Navigator Encrypt 3.9.0
- Issues Fixed in Cloudera Navigator Encrypt 3.8.0
- Issues Fixed in Cloudera Navigator Encrypt 3.7.1
- Issues Fixed in Cloudera Navigator Encrypt 3.7.0
Issues Fixed in Cloudera Navigator Encrypt 3.16.0
Issues Fixed in Cloudera Navigator Encrypt 3.15.0
See New Features and Changes in Cloudera Navigator Encrypt for new features in Cloudera Navigator Encrypt 3.15.0.
Issues Fixed in Cloudera Navigator Encrypt 3.14.0
See New Features and Changes in Cloudera Navigator Encrypt for new features in Cloudera Navigator Encrypt 3.14.0.
Issues Fixed in Cloudera Navigator Encrypt 3.13.0
See New Features and Changes in Cloudera Navigator Encrypt for new features in Cloudera Navigator Encrypt 3.13.0
Issues Fixed in Cloudera Navigator Encrypt 3.12.2
Cryptsetup Password Quality Check Skipped
The Navigator Encrypt prepare operation was failing on systems running RHEL 7.x because the 'Password quality check' of cryptsetup was enabled by default. It is possible that this could impact other operating systems.
The navencrypt-prepare command now skips the 'Password quality check' whenever it is enabled by default. This update has been implemented for all distributions supported by Navigator Encrypt.
Issues Fixed in Cloudera Navigator Encrypt 3.12.0
See What's New in Cloudera Navigator Encrypt 3.12.0 for new features in Cloudera Navigator Encrypt 3.12.0.
Issues Fixed in Cloudera Navigator Encrypt 3.11.0
See What's New in Cloudera Navigator Encrypt 3.11.0 for new features in Cloudera Navigator Encrypt 3.11.0.
Issues Fixed in Cloudera Navigator Encrypt 3.10.0
See What's New in Cloudera Navigator Encrypt 3.10.0 for new features in Cloudera Navigator Encrypt 3.10.0.
Issues Fixed in Cloudera Navigator Encrypt 3.9.0
Issues Fixed in Cloudera Navigator Encrypt 3.8.0
Encrypting or decrypting a file or folder with a space in the name generates extraneous message
/usr/sbin/navencrypt-move: line 233: [: /root/encrypt: binary operator expected
This message can be safely ignored.
Cloudera Bug: KT-1335
Running navencrypt-move twice on the same file does not fail properly
ln: creating symbolic link '/path/to/file/to/encrypt' to '/path/to/mountpoint/category/path/to/file/to/encrypt': File exists
Cloudera Bug: KT-1707
Running navencrypt-prepare --undo removes all similar entries from /etc/navencrypt/ztab
Running navencrypt-prepare --undo /path/to/mountpoint removes all similar entries from /etc/navencrypt/ztab. For example, if you have mountpoints named /mnt/data, /mnt/data1, and /mnt/data2, running navencrypt-prepare --undo /mnt/data removes /mnt/data, /mnt/data1, and /mnt/data2 from the Navigator Encrypt mount table (/etc/navencrypt/ztab).
Cloudera Bug: KT-1928
Encrypting or decrypting in parallel fails
keyctl_unlink: Required key not availableNo data is lost, because the source data is not removed, but you must re-run the failed operations sequentially.
Cloudera Bug: KT-1036
Issues Fixed in Cloudera Navigator Encrypt 3.7.1
Pressing Ctrl + C during rule creation corrupts rule file
[ERROR] Cannot parse ACL format: ACL header is not found: Did you type an incorrect key?
Issues Fixed in Cloudera Navigator Encrypt 3.7.0
Kernel module reported by SLES as tainted kernel
The Navigator Encrypt kernel module is identified as a tainted kernel by SLES.
Categories: Encryption | Fixed Issues | Navigator | Release Notes | Troubleshooting | Upgrading | All Categories