Known Issues and Workarounds in Cloudera Navigator Encrypt
The navencrypt status --integrity command does not detect loop devices properly
Running the navencrypt status --integrity command on a system using a loop device incorrectly reports that the backing file does not exist.
Navigator Encrypt 3.12 and earlier does not support specific kernels
Versions of Navigator Encrypt 3.12 and earlier do not support the following kernels:
Note that this is not specific to a particular platform; rather, it is specific only to the kernels listed here.
Workaround: Use a kernel other than those listed here.
The Navigator Encrypt kernel module does not build on Ubuntu 14.04.04
The Navigator Encrypt kernel module does not build on Ubuntu 14.04.04 (kernel version 4.2).
Using screen utility with Cloudera Navigator Encrypt does not work
Running Cloudera Navigator Encrypt commands within the Linux screen utility does not work correctly.
The navencrypt exec command does not work
Using navencrypt exec to run a single command without having a matching ACL rule does not work.
Workaround: Add a temporary ACL rule to allow the command you want to use.
Sophos antivirus is not compatible with Cloudera Navigator Encrypt
Kernel panics have been observed on machines running both Sophos antivirus and Cloudera Navigator Encrypt.
Workaround: None. Do not use Sophos antivirus in conjunction with Cloudera Navigator Encrypt.