Navigator Encrypt 3.8.0

OS Requirements

• Linux kernel 2.6.19 or later (RHEL and CentOS can use 2.6.18-92 or later)
• RHEL-compatible 6.4, 6.5, 6.6, 7.1
• SLES 11 SP2/SP3

  Note: SLES 11 does not support the ext4 filesystem.

• Ubuntu 12.04, 14.04
• Debian 7

Important: With the exception of Cloudera Navigator Encrypt, Cloudera Enterprise is supported on platforms with Security-Enhanced Linux (SELinux) enabled. However, policies need to be provided by other parties or created by the administrator of the cluster deployment. Cloudera is not responsible for policy support nor policy enforcement, nor for any issues with such. If you experience issues with SELinux, contact your OS support provider.

Supported command-line interpreters:

• sh (Bourne)
• bash (Bash)
• dash (Debian)

Note: Navigator Encrypt does not support installation or use in chroot environments.

SELinux Requirements

SELinux must be disabled for Key Trustee installation and operation. Modify /etc/selinux/config to set SELINUX=disabled and reboot the system for the change to take effect.

Network Requirements

For new Navigator Key Trustee Server (5.4.0 and higher) installations, Navigator Encrypt initiates TCP traffic over port 11371 (HTTPS) to the Key Trustee Server. For upgrades and Key Trustee Server versions lower than 5.4.0, Navigator Encrypt initiates TCP traffic over ports 80 (HTTP) and 443 (HTTPS) to the Navigator Key Trustee Server.

Entropy Requirements

Cryptographic operations require entropy to ensure randomness.

You can check the available entropy on a Linux system by running the following command:

$ cat /proc/sys/kernel/random/entropy_avail

If the entropy is low (500 or less), you must increase the entropy in the system. You can do this by installing rng-tools and starting the rngd service. For example, on RHEL-compatible systems:

$ sudo yum install rng-tools
$ sudo echo 'EXTRAOPTIONS="-r /dev/urandom"' >> /etc/sysconfig/rngd
$ sudo service rngd start
$ sudo chkconfig rngd on

Internet Access

You must have an active internet connection to download many package dependencies, unless you have internal repositories or mirrors containing the dependent packages.

Maintenance Window

Data is not accessible during the encryption process. Plan for system downtime during installation and configuration.

Administrative Access

To enforce a high level of security, all Navigator Encrypt commands require administrative (root) access (including installation and configuration). If you do not have administrative privileges on your server, contact your system administrator before proceeding.

Package Dependencies

These dependent packages are native to most Linux operating systems, and are resolved by your distribution's package manager during installation.

• dkms
• kernel-devel
• keyutils
• ecryptfs-utils
• gettext
• gettext-libs
• libgomp
• libztrustee
• navencrypt-kernel-module
• binutils
• cloog-ppl
• cpp
• gcc
• glibc-devel
• glibc-headers
• kernel-headers
• libmpc
• mpfr
• ppl
• Updates to glibc and glibc-common

Installation works with gcc, gcc3, and gcc4.

What's New in Cloudera Navigator Encrypt 3.8.0

• Support for RHEL 7.1
• Support for automatically mounting loop devices on boot (see Block-Level Encryption with a Loop Device for details)
• Automatic failover for high availability Navigator Key Trustee Servers (see Registering with Key Trustee Server for details)
• The ability to restore deleted local mount encryption keys (MEKs) from Key Trustee Server by UUID