Zum Inhalt springen

u.trust LAN Crypt for iOS / iPadOS · English

General preparations and setup

PDF herunterladenHerstellerquelleImportierter Dokumentationsstand – bitte Produktversion beachten.

Kapitel: General preparations and setup
  1. Übersicht
  2. What is u.trust LAN Crypt for iOS / iPadOS?
  3. Supported encryption algorithms for file encryption
  4. General preparations and setup
  5. Policies
  6. Rolling out policy files and certificates using MDM
  7. Deleting policy file and user certificate
  8. Open, edit, encrypt, decrypt and share files
  9. Logging
  10. Compatibility with Cloud Services
  11. Reporting Security Vulnerabilities
  12. Technical support
  13. Legal notice

For security reasons, the Utimaco LAN Crypt app requires a passcode to be set for the device. When the app becomes active, it checks for the presence of a device passcode and if it finds that the device is not protected, it blocks usage until a device passcode has been set. Never use an easy-to-guess passcode, such as “1234” or “000000”. Only with a secure passcode you can prevent unauthorized access to your confidential data, in case your device is lost or stolen. In general, Utimaco recommends to erase the policy file and certificate on your Apple device, if the device is not in use for a longer period of time, or if you exchange your device for a new one (see Deleting policy file and user certificate).

Note

  • When the device passcode is turned off, the user certificate password is removed and must be re-entered after the device passcode is turned on again.

Providing the configuration data

After leaving the u.trust LAN Crypt for iOS / iPadOS welcome screen, you will be prompted to provide the configuration data:

Note

  • If SMB shares are used to distribute configuration files, the settings view shows an additional Network section. This allows to clear or enter the SMB credentials. When deleting the SMB credentials, downloaded configuration files are deleted as well.

Managing encryption keys

Managed keys and password-based keys can be both found within the settings. Managed keys originate exclusively from the given policy file, whereas password-based keys can be freely created, renamed and deleted inside the related settings. Renaming a key does not change the generated key used for encryption.

Note

  • Password-based keys can also be created within the action of encrypting a file. These keys are then automatically added to the saved list of password-based keys.

  • By successfully decrypting a file with a password-based key, the used key will also be automatically added to the saved list of password-based keys.

  • Passwords used for generating password-based keys can also still be inspected after they have been created.