CSSv5.0.0 en:65668014

Aus Cryptshare Documentation
Wechseln zu:Navigation, Suche

Important Update Notes

Updating from older Versions

Consider previous update notes
If you are updating from an earlier Cryptshare Server version, you also need to consider all the previous update notes as they contain vital information for the proper operation of the server.
Not following these notes may lead to unexpected behavior after the update, such as failing SSL connections due to Cipher Suite changes.

New Database

This update introduces a new database backend. Before updating it is strongly recommended to read the information concerning the Database Migration.

Note on the login process for a pending postupdate Due to the database changes in the background, the first login process takes longer than usual (up to one minute).

Log in to the administration interface:

Due to changes in the login mechanism there are changes for administrative users.

Administrative users who have existed since a version prior to Crypthshare 4.3.0 and have not logged in until the update to Cryptshare 4.7.0 must be reset by the administrator performing the update in order to log in again.

Changed Archiving Configuration


Due to underlying changes, the way how time-based information is processed in the archiving metadata templates has changed. If you previously customized the metadata template for the file-system or SCP archiving connector, please migrate the custom template as described below.

Consequences of omitting this manual step
Please note, that if the archiving meta-data configuration has been adjusted, the update process cannot automatically update this configuration. The migration of this configuration must be done manually after the update has completed. If this manual step is omitted, the archiving meta-data will be incomplete for future transfers. If this configuration has not been adjusted, it will be updated automatically.

Changed Velocity Context variables

The table below shows all variables which need to be updated with the value listed under New in order to have the same output as before the update.

Variable Old New
provisionDate ${provisionDate} ${date.toDate(${provisionDate})}
expirationDate ${expirationDate} ${date.toDate(${expirationDate})}

Changed method calls

As a consequence of the changes in above mentioned variables, method calls on these variables have changed as well. The table below shows all method calls which need to be updated with the value listed under New in order to have the same output as before the update.

Variable Old New
provisionDate ${provisionDate.getTime} ${date.toDate(${provisionDate}).getTime()}
expirationDate ${expirationDate.getTime()} ${date.toDate(${expirationDate}).getTime()}

Changed System-Log Configuration

Due to changes in the system's structure the configuration file to set the 'system-log' settings will be modified during the post update process. The file `resources/logback.xml` will be replaced by the a new configuration file.

Backup modified logback.xml manually before the update
If the file resources/logback.xml has been manually modifed, it is advised to make a backup copy of it before starting the update process so its configuration can be applied to the new logback.xml after the update has completed.

Update the logback.xml after post update
# Finish the post update procedure.
  1. Navigate in the administration interface to the menu System-Settings → Log Settings→ System-Log.
  2. Copy the contents of the old `logback.xml` into the input field.
  3. Navigate to the section marked by `` .
  4. Add this line: <logger name="com.cryptshare.server" level="info" />
  5. Click Save changes.

Language Packages

Due to structural changes in the language packages, all supported server language packages will be updated automatically, customized language packages will be removed during the update process (a backup is done before). If more language packages are needed, it is required to download and install them again.

Delta-File for changed passages

In case your language packages have been modified, the attached delta-file delta\_english\_lp\_4.6.1\_to\_4.7.1.txt can help you to locate the changes in this update and re-apply the modifications.

Click here to see how the delta file for language packages is built.


Removed Files
Files listed in this section have been removed from the language package entirely.

New Files
Files listed in this section have been added to the language package.

Modified Files
Files listed in this section have been modified, which can be one of the following cases:
  • Keys have been removed
  • Keys have been added
  • Keys have been modified
<path and file name>
---Removed keys---
---New keys---
---Modified keys---
KEY: <affected key>
OLD: <former key & value>
NEW: <new key & value>
In case of a modification, the affected key, its old value and its new value is shown.

Additional Changes

  • Resolved an issue for LDAP based rules where deactivated users were not considered properly.
  • Resolved an issue where archiving via SCP was not removing files again after they have been marked ‘ready’.
  • Resolved an issue where the recipient proposal list in the user interface was not shown under certain circumstances.
  • Resolved a minor issue where custom CSS for advanced user interface design changes was not reloaded properly.
  • Resolved an issue where EML content was not loaded in the content viewer of the user interface under certain circumstances.
  • Resolved minor layout issues in the content viewer for EMLs with attachments.
  • Resolved an issue where the confidential message subject was revealed in email notifications under certain circumstances.
  • Resolved an issue where the language setting of the sender was not saved when using add-on products.
  • Added the possibility to upload only a confidential message via the webservice interface.
  • Resolved several typos in the administration interface and the user interface.
  • Resolved minor layout issues with long email addresses in the user interface.
  • Improved logging details for several administrative operations.
  • Several core libraries have been updated.
  • The Java Runtime Environment has been updated to v11.0.9.