Contents
-
Introducing Nomad
-
Implementing Nomad
-
Using Nomad
-
Nomad features
-
Troubleshooting
-
Training
-
Reference
-
Nomad app
-
Nomad tools
-
Nomad OS Deployment task sequence actions
-
Supported Platforms
-
1E Companion Products
-
Communication ports
-
Log files
-
Nomad architecture
-
Nomad command-line switches
-
Nomad installer properties
-
Nomad registry values
-
Nomad return codes
-
FIPS compliant communication encryption
-
Glossary
-
Nomad Product Packs reference
-
Nomad release information
-
Scripts
-
Nomad app
Encryption types
Nomad provides two types of encryption, its default 40-bit RC2 encryption algorithm and FIPS compliant encryption. You can set the encryption type used by Nomad during installation or by modifying a Nomad registry entry.
Nomad clients running different encryption types will be unable to communicate with each other. If you want to use FIPS compliant encryption and earlier versions of Nomad are already deployed, you should roll out Nomad using its default encryption standard. Once all clients have been upgraded, change the encryption level to FIPS compliant.
Installing Nomad with FIPS encryption
FIPS encryption can be set when you enable Nomad in the 1E Client. This is done by checking the Use FIPS encryption checkbox on the Nomad screen of the 1E Client installer, for more information refer to Installing the 1E Client for Nomad.
You can also set FIPS encryption with the MODULE.NOMAD.USEFIPS installer property.
Setting FIPS encryption post-installation
To change Nomad's encryption type after installation you can modify the EncryptionType registry value. By default, this is set to 0, for standard Nomad encryption, unless the Use FIPS encryption checkbox was checked during installation, in which case it is set to 1.