This document contains the following topics:

• CompanyCRYPT update description
• Description of previous updates
• Prerequisites
• Installing this CompanyCRYPT version
• Removing the CompanyCRYPT version

This Installer/Updater will improve your CompanyCRYPT to version 1.5.0 (Build 768).
It includes all previous releases, maintenance packs and updates since the initial v1.4.0 (Build 537)


Added Features / Abilities:

• AdHoc encryption - EML Format
  AdHoc encryption now offers an additional 'packaging format' that provides a far better usability. Until now the content of the 'original message' zip file basically contained separate attachment files effectively resulting in a break of media.
  The EML format however is a single file that contains the entire message in it's original form (header, MIME structure, etc.). The recipient simply unpacks the password protected zip file and double-clicks on the extracted EML file. All common mail clients (Outlook, Thunderbird, ...) will simply import this message. After import it will look as the message was received via SMTP. It will even appear in the original time related order.
• Key harvest from key server - More Automation
  So far key server queries only supplied keys during processing without any caching or storing facility behind it. This has changed and now available keys may be automatically collected in the import area. From there they can be picked up by the auto-import and if usable and/or trustworthy transferred into the key stores (possibly avoiding further queries).
  The same saving mechanism is also available when doing manual test queries via the UI (Tab 'Key Server' -- Sub-menu 'External Keyserver'). Thereby it has become much more easy to bring available keys in use.
• S/MIME signature verification - Modell selection available
  The signature verification modell for S/MIME signatures can now be selected, which makes signature verification more flexible.
  [NOTE: The below rules apply on signatures made on data as well as signatures made on certificates.]
  • SHELL Model: All signatures need to valid at time of verification
  • HYBRID Model: All signatures need to valid when the data was signed
  • CHAIN Model: Each signatures need to be valid when made
• Compatibility with prolonged PGP keys
  Although not seen very often PGP keys can have their validity prolonged. The difference to S/MIME is, that the key ID and the fingerprint remain the same. This of course has to be considered when identifying keys in the key store by their fingerprint. It can then have two different results for the same fingerprint. CompanyCRYPT processing has been enhanced to support prolonged keys.
• Display improvement
  As nowadays browser continue to evolve some amendments were necessary to make the UI work as usual. This is visible when holding the focus on a key as well as table structures. Also the file names in the import area were changed back to display the common name and email. Additonally the key lists can now be filtered to custom values in the columns.
• S/MIME Signing algorithm selection
  It is now possible to select the algorithms for encryption and signing for the S/MIME formats. It's is however recommended to stay with the defaults (des3 / sha1) unless security requirements occur. For example, some customers changed the encryption algorithm to AES only to learn that even encryption systems of large banks seem to be not yet ready to cope with this.

Problems addressed in this release:

• Reprocess Service
  Two processing flaws have been identified in the recipient splitting of the Reprocess Service. It resulted in recipient groups that were not fully separated. This again lead to a loop effect as the processing continued to request further recipient splitting; eventually leading to 'undetermined'.
  • Automatically imported keys were not available for recipient splitting
    The signaling mechanism between auto-import and keystore-reload apparently wasn't working as designed resulting in the described effect (undetermined). The Reprocess Service now is enhanced to detect keystore changes and perform the reload automatically whenever they occur. This provides a permanent solution.
  • Recipient splitting did not consider keys available from key server
    Although being caused by a different reason (ill-designed conditional) the effect was the same. The recipient splitting was not properly done. The routine has been corrected and is now taking available keys from key server into account.
• Expired keys used for encryption + Auto-signing did not use the newest key
  The XML key store system did have an unfortunate bug that came into effect when auto-encryption (or -signing) found multiple keys for an email address. Instead of making an intelligent choice the first that appeared was used. Even worse, for encryption even expired keys were used. The routine selecting the keys has been reworked and is now only using valid keys for encryption. The auto-signing will look for the newest key (by 'valid from' date).
• Synchronization - CompanyCRYPT Slave displayed as outdated
  Once found it became clear that this only was a display problem in the system overview. Due to minor bug this status was possibly indicated during the first month of the year. This has been corrected
• Decryption problem with Inline-PGP
  Two issues were found while decrypting Inline-PGP messages.
  • Inline PGP signature
    Normally, if processing comes across a so called 'detached signature file', a token is to the header to track processing. Incidentally for PGP it compared the token with the wrong block of data, declaring the token invalid. Invalid token lead to a normal decrypt/verify that would add a new token. Which is invalid again in the next go. After six or seven steps the processing exits with a decrypt fail. This has been fixed.
  • Inline PGP decrypt did not detect PGP Block
    It turned out, that (in very rare instances) if a PGP block has either no trailing CR/CRLF (which is not in accordance to RFC 2440) or was terminated by a softbreak, the detection failed and no decryption/verification/key scan took place. The detection routines have now been modified to work independently from the trailing characters.
• Triggered-Encryption exception falsly applied under Best-Effort-Encryption -
  The exception list no longer has an influence on Best-Effort-Encryption.
• Memory leakage - Operational and Reprocess Service
  Under MS-Windows versions 2008 and later a memory leakage problem was identified. It did not affect operations or message processing. However small portions of memory (~20kB) were kept in GnuPG and S/MIME zombie processes. The problem was not visible via the taskmanager (besides the missing memory). Using a tool like RAMMap finally revealed the problem. Over time and extend of usage this could lead to a memory shortage affecting the operating system. This too has been fixed.

Compatibility

• Tested with MS Windows Server 2012 / MIMEsweeper for SMTP 5.6
  This CompanyCRYPT version has been tested to work under MS Windows Server 2012 as well as MIMEsweeper for SMTP v5.6

Security issues

• S/MIME Module (OpenSSL) update to v1.0.1i 06 Aug 2014
  The latest version of OpenSSL is part of this update. So far none of the development steps are of any effect to CompanyCRYPT. The following links provide more details.
  • OpenSSL Newsflash [06-Aug-2014]
  • OpenSSL Security Advisory
• PGP Module (GnuPG) update to v1.4.18
  The latest version of GnuPG is part of this update. Besides small performance upgrades no noteworthy changes in regard to to CompanyCRYPT are part of this release. The following link provides more details.
  • [Announce] GnuPG 1.4.18 released
  
  

Topics covered by the previous releases:

1.4.6 (Build 747)

Added Features / Abilities

• Change of key store structure - XML based key stores
  Various requirements have resulted in the need to change the handling of keys. Initially this technology was planned for field operation in version 2.0, but customer inquiries and an extra development effort made it possible benefit from it to a meaningful extend. The full potential will be used in oncoming versions. Already available are
  • Using keys with no built-in email address (via 'Encrypt Alias')
  • Using multiple keys for the same Email address.
  • Swift key list display even with hundreds of keys.
  • Easier and more flexible Site-To-Site configuration
• PGP key server
  The former S/MIME key server query has been extended to allow queries on PGP key server. This feature comes in two flavours: One method is based on LDAP which allows to query PGP-Universal server. The other method is based on HTTP (or sometimes referred to as HKP). This is mainly used by 'open' internet PGP key server. However using this source requires careful consideration, as anyone can upload keys there for just any address. However in the bottom line this feature enables CompanyCRYPT to query just about any key server.
• Language Templates
  The implementation of message templates has been extended. About all templates files can be localised and addressed via standard 2-Letter identifiers. New language files can be easily added. The UI offers language selections. If the built-in range needs to be extended, contact CompanyCRYPT support to receive guidance on how to achieve this.
• Detached S/MIME signature on gz compressed content
  There are regulations in the utility sector that allow the use of gz compression algorithms to be used on signed data. The processing of detached S/MIME signature files has been extended to support this, as described in these regulations. This includes: Only support for gz compression, no password, single file content and the use of ...txt.gz file name extension to identify this special processing requirement.
• SyncManager - Additional Reprocess service control
  The SyncManager utility is mainly used to quickly manage CompanyCRYPT Slave clients without setting up a WebUI. However until now it was not possible to control the Reprocess service as it used to with the Operational service. Now both service status can be seen in the utility including a start/stopp functionality.

Problems addressed:

• MS Exchange - Problems with split emails
  There is a (supposing anti-spam) feature built into MS Exchange that prevents multiple messages with identical 'message-IDs' being delivered. Unfortunately when a message is split for different recipients for policy reasons only the first message is delivered, the others are discarded. This fatality has been fixed by removing the message-ID from split-messages. The message ID is automatically added once it passes the MIMEsweeper again.
• Windows Server 2008 R2 - Synchronisation not working
  On these OS versions the synchronisation never completed successfully. After synchronising and downloading all files the service wasn't able to update the time stamp of the files and hence ended in a roll-back. The implementation of a different time function has solved this issue.
• VeriSign and Web.de certificates - Problems involving signature or certificate validation
  It turned out that S/MIME certificates from VeriSign and Web.de carry certain differences in regard to issuer key ID. Especially when gathering certificates to establish a certificate chain (for signature or trust verification) a different approach has to made to be successful in this. By including key serial information and 'known' key IDs in the process the functionality has been restored.
• Key details display - Key-ID field not showing correct content
  Certains S/MIME certificates do not follow conventional patterns while using the 'Issuer Key ID' field. An unnecessary amount of data was added by the manufacturer of the certificate and hence displayed in the CompanyCRYPT UI. This has been modified to represent the data correctly.
• Encrypted 'Read-' and 'Delivery-notifications - Change of processing
  Although mime parts of the type 'message/disposition-notification' per RFC are not to be encrypted, we had reports from customers where external partner did exactly that. As there is no noticeable decrease in performance to be expected, such mime parts arer no longer excluded from decryption.
• Reprocess service - Recipient splitting for automatic encryption not working under certain conditions
  The reprocess service failed to detect the condition to split a message if one recipient has a vaild S/MIME certificate and the other recipients certificate is present, but expired. This has been corrected.

Security issues

• S/MIME Module (OpenSSL) update to v1.0.1c 10 May 2012
  The latest version of OpenSSL is part of this update. So far none of the development steps are of any effect to CompanyCRYPT. The following links provide more details.
  • OpenSSL Security Advisory [10-May-2012]
  • Announcement: OpenSSL version 1.0.1c
• PGP Module (GnuPG) update to v1.4.12
  The latest version of GnuPG is part of this update. Besides small performance upgrades no noteworthy changes in regard to to CompanyCRYPT are part of this release. The following link provides more details.
  • [Announce] GnuPG 1.4.12 released
  
  

Install this CompanyCRYPT version on the following versions only:

• CompanyCRYPT v1.4.6 (Build 746) or higher

The account under which this Installer/updater is executed requires:

• Read/Write/Change access to the entire CompanyCRYPT installation folder.
• Start/Stop permission for the 'CompanyCRYPT Reprocessing Service', the 'CompanyCRYPT Operational Service' and the 'MIMEsweeper for SMTP Security service'.

Before installing this CompanyCRYPT version, ensure that you have read the Prerequisites section of this ReadMe.

To install this CompanyCRYPT version, follow the instructions below.

1. Make a file copy of the complete CompanyCRYPT folder
   It is not required to stop the services for this step.
   
   
2. Execute 'CompanyCRYPT_v150_768_Setup.exe' and follw the instructions
   Relevant and still active services are stopped and restarted afterwards.
   
   
3. Start either SyncManger or WebGUI
   With this step some initialisation is performed. It is advisable to also confirm the operational status of the services mentioned above.
   
   

If you experience problems during or after installing this CompanyCRYPT version, you should contact the CompanyCRYPT support immediately

To remove CompanyCRYPT, go in the Windows control panel and under 'programs and functions' select de-install CompanyCRYPT. Please consult the CompanyCRYPT Installation Guide for a detailed description of this procedure.