CSSCurrent en:Version 7.0.0

Release Date: 13.02.2024

Important Update Notes

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.

In case your language packages have been modified, the attached delta-file Datei:Delta english lp 6.2.0 to 7.0.0.txt can help you to locate the changes in this update and re-apply the modifications. The structure of this file is explained in Language Pack Changes.

Cryptshare Update Process Changes

• Flexible Update Paths: Direct updates to the most current version are possible, regardless of the currently installed version.
• Conditional Manual Updates: For versions that require manual intervention, the update process halts, ensuring all necessary configurations are properly handled.
• Rollback on Failure: Automated rollbacks preserve system integrity if an update fails at any step.
• Smart Update Checks: The system displays the most advanced version that can be installed unattended.

Enhanced Automatic Update Features

• Update Warnings for Manual Steps: Alerts users when the latest version cannot be updated automatically due to required manual steps.
• Alternative Version Notification: If a lower version is available for automatic update, this will be mentioned in the warning.
• Optimized Unattended Installation: The system automatically selects the highest version available for unattended updates.
• Admin Notifications: Emails notify administrators of available updates, differentiating between manual and automatic options.

Advanced Post-Update Automation

• Non-Interactive Post-Update Steps: If no administrator action is required, post-update steps run automatically and non-interactively.
• Automatic Return to Operation: After an update, the Cryptshare Server automatically returns to a usable state.
• Critical Failure Handling: In case of critical failures during post-update steps, an automatic rollback to the previous state is triggered.
• Non-Critical Failure Notifications: Non-critical failures are displayed on the "Status" page, visible only to users with "Administrator" or "Config Admin" roles. These messages remain until confirmed by one of these users.
• Update Success Notification: After a successful update, a success message and a link to the release notes are displayed on the "Status" page.
• Backup Restoration Option: Information about the possibility to restore the pre-update backup is mentioned post-update.

Enhanced Transfer Policy Configuration through CSV

Administrators can now fully configure transfer policies by importing a CSV file. With this update, every configuration input available through the admin web application's wizard can also be set via CSV import. This enhancement provides a comprehensive and efficient method for managing transfer policy settings, ensuring greater flexibility and control.

Improved Validation of Generated Passwords

An issue has been resolved that caused (in rare cases) generated passwords to be rejected because they did match the configured password policies. As part of the solution, the password policy is now checked on saving, to ensure that it allows a sufficient number of secure random passwords.

The password policy is also checked during the update process and may need to be adjusted.

Legacy Archiving Update

Legacy archiving functionality, which has been prone to issues and is no longer maintained, has undergone significant changes:

• Feature Flag Introduction: A new feature flag has been introduced in the properties settings to control the enabling of legacy archiving. (Please contact our support if you need the feature flag to enable Legacy archiving).
• Admin Interface Visibility: Legacy archiving options are now only displayed in the Admin Interface if the feature is actively enabled.
• Default Setting: The feature flag for legacy archiving is disabled by default, reflecting our move towards file based archiving solutions.
• Post-Update Notification: If legacy archiving is configured, information will be displayed on the Post-Update screen. This includes a link to documentation for Local File Archiving, guiding administrators on transitioning to newer, supported archiving methods.

Additional Changes

• Enhanced IP Address Configuration in Policy Settings: Policy configurations now support simultaneous IPv4 and IPv6 address inputs, applicable to both direct settings and CSV imports. Validation errors no longer redirect to an error page; instead, the wizard stays open, displaying errors for immediate correction. Additionally, previous issues with IPv6 compatibility have been resolved, ensuring all valid IPv6 addresses are now accepted, improving system reliability and flexibility.
• Fixed caching issue: We've improved Cryptshare's log file delivery by fixing the issue that the latest files are not downloaded because of cache, ensuring direct access to the latest log files without complications.
• Update Check Task Improvement: Resolved an issue where not modifying the update URL before running the UpdateCheckTask led to a NullPointerException (NPE). This fix ensures that notifications are sent correctly without errors.

• JRE Update Enhancements: We've addressed the issue where symlinks were broken due to incorrect POSIX permissions by updating the Java Runtime Environment (JRE). The new JRE update includes an improved handling mechanism that retains the archive format, rather than extracting it, effectively resolving the permissions issue and ensuring symlink integrity.

• Appliance Settings and Update Checks: Fixed an error that occurred during appliance settings adjustments and refined the REST API to include sender notifications.
• UI and Styling Fixes: Addressed an issue where large file names disrupted UI styling, and resolved minor XSS vulnerabilities in notification messages for better security.
• Library Upgrades: Upgraded Java Runtime Environment (JRE) and Spring libraries to enhance performance and security.
• Admin UI Consistency: Resolved inconsistencies where custom link settings were not properly reflected in the admin UI, ensuring a more reliable configuration experience.