Humber File Structure

Humber creates a journal file.  This file shows the time of every Humber transaction and indicates whether it is an encryption or decryption.  It then shows the name of the encrypted file alongside the name of the plain language file.  This allows the operator to pair up the files if any need to be re-encrypted or re-decrypted.  The journal file is essential in this capacity because there is no correlation between the original file name and the encrypted file name.  This file also allows the timing of messages to be tracked.  The journal file resides in same directory as the executable and is named "Journal.dat".

Humber creates six subdirectories, if not already present.  Assuming the name of the installation directory is "humber" the six subdirectories would be:

  1. "humber/messages".  This contains all the files for encryption.  Once a file has been created, it must be placed in this directory before it can be encrypted.
  2. "humber/crypto".  This contains all the encrypted files ready for transmission.  All the file names are created automatically by Humber during the encryption process and each consists of the system date followed by a random, 8 character, hexadecimal number.
  3. "humber/encrypted".  All messages are moved automatically from the messages directory to this directory when they have been encrypted.
  4. "humber/cripin".  This contains all the enciphered messages for decryption.  These will have been created by a Humber application and transmitted as encrypted files.  Once received, messages for decryption must be placed in this directory.
  5. "humber/plaintext".  This contains all the decrypted plain text files with original file name, which are automatically added to this directory by Humber.
  6. "humber/decrypted".  All messages are moved automatically from the cripin directory to this directory when they have been decrypted.