to download - Secure Support - SafeNet

Chapter 4AdministrationSleeping Domains/EnvelopesDuring startup, ProtectFile reads the tag file of all registered domains/envelopes.Sometimes this is not possible (for example, the CD with the domain/envelope isnot inserted or the server hosting a domain/envelope is not available). Suchdomains/envelopes are called ―sleeping domains/envelopes.‖ They are marked asAsleep in the View Domains/Envelopes dialog.Typically, their existence is of no importance, as the corresponding files are notavailable. However, it may happen that a sleeping domain/envelope becomesavailable later on (for example, the CD is inserted or the network server isrestarted). In this case, ProtectFile offers the possibility of waking thesedomains/envelopes. In order to do so, the user has to click on the ProtectFile icon inthe task bar.Nested Domains/EnvelopesIt is not possible to define a domain/envelope inside an existing domain/envelope.NTFS CompressionThe NTFS compression attribute and the encryption are not compatible with oneanother. Compressed files should not be encrypted, and encrypted files shouldtherefore not be compressed in order to avoid file corruption.Renaming Envelope Root FolderEnvelope folder structure consists of a root (top-level) folder and all of itssubfolders. Renaming an envelope‘s root folder is not supported by ProtectFile, butrenaming all subsequent subfolders is permitted.Using a New Token with a Newly Issued CertificateLogging on to ProtectFile Premium MSPKI using a new token/smartcard with anew certificate on it may result in an error. This is due to the fact that ProtectFilewill still be looking for the private key associated with the previously used (―old‖)certificate located on the previously used (―old‖) token/smartcard.To circumvent this scenario, the user must initially log on to ProtectFile with the―old‖ token to allow ProtectFile to query the server for the new certificate anddecrypt the existing configuration (and then re-encrypt it) using the new certificate.Incidentally, the user may experience a log on error while using this method. Theuser must then log on again using the new token/smartcard. The user will not beable to access registered envelopes (or get their content in plain text form) untilthese envelopes get administered and, therefore, encrypted with the new public key.38 © SafeNet, Inc.