Aktuelle Version vom 17. Mai 2024, 06:41 Uhr

Release Date: 21.05.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 Enhancements

We have updated the Cryptshare update process to improve clarity and functionality.

With this update, it is possible for the updates to be installed unattendedly, streamlining the upgrade process to the latest available version through multiple intermediate releases. The update process is automatic, eliminating the need for manual interaction unless specific configurations require administrative attention.

The system now intelligently determines the most suitable update path, considering whether updates can proceed automatically or require manual intervention, and whether they are attended or unattended.

The update process is documented in this article.

Enhanced Transfer Policy Configuration through CSV

Administrators can now fully configure transfer policies by importing a CSV file. This update ensures that all settings available through the administration interface policy wizard are now configurable via CSV import. The CSV export now also contains all parameters that can be configured in the policy wizard. This enhancement simplifies e.g. the process of transferring fully configured policies from a test server to a production server.

Improved Validation of Generated Passwords

An issue has been resolved that caused (in rare cases) generated passwords to be rejected because they did not 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.

Discontinuation of "Legacy Archiving" connector

With this release, the outdated "Legacy Archiving" connector has been disabled by default to align with our transition towards the more modern and powerful "Local File System" archiving connector.

Before performing an update, you can check the menu "Transfer Processing" -> "Archiving" if there is a Legacy Archiving connector configured. More information about the archiving feature can be found in this article. If legacy archiving is currently configured, please refer to the migration guide from the Legacy Archiving to the Local File System archiving. In case, a Legacy Archiving connector is detected during the Post Update, a reminder hint message of the continuation will be presented in the Post Update screen.

Network Patterns for Policy Rules

Policy configurations now support simultaneous IPv4 and IPv6 address inputs, applicable to both direct settings and CSV imports. Previous issues with IPv6 compatibility have been resolved, ensuring all valid IPv6 addresses are now accepted. Additionally, an issue in the policy wizard regarding network matchers was resolved.

Additional Changes

Resolved an issue where downloaded log files might have been cached by the browser.
Resolved an issue that prevented sending of notifications during update check task.

Resolved an error that occurred during appliance settings adjustments.
Resolved an issue in the REST API where the sender notification flag was not applied correctly.
Resolved an issue where large file names disrupted UI styling.
Resolved an XSS issue in notification messages.
Resolved various issues with the administration of notification email subjects and signatures. They now require unique names, and can be detached from policy rules.
Resolved an issue where the order of Custom Links was not reflected in the configuration menu. Changes to Custom Links are now reflected directly in the Web App, without starting a new session.
Upgraded Java Runtime Environment (JRE) and Spring libraries.

@@ Zeile 6: / Zeile 6: @@
 {{NoteBox|title=|content=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 [[{{NAMESPACE}}:Language Pack Changes|Language Pack Changes.]]
-== '''Cryptshare Update Process Enhancements''' ==
+== Cryptshare Update Process Enhancements ==
-We have updated the Cryptshare update process to improve clarity and functionality. The system now intelligently determines the most suitable update path, considering whether updates can proceed automatically or require manual intervention, and whether they are attended or unattended.
+We have updated the Cryptshare update process to improve clarity and functionality.
-'''Update Mechanics Explained:'''
+With this update, it is possible for the updates to be installed unattendedly, streamlining the upgrade process to the latest available version through multiple intermediate releases. The update process is automatic, eliminating the need for manual interaction unless specific configurations require administrative attention.
-# '''Update Path Selection:''' The system automatically detects the optimal route for updates. If the latest version requires manual steps, the update process will pause and notify the user. For automated environments, it selects the highest version that allows for an unattended update.
+The system now intelligently determines the most suitable update path, considering whether updates can proceed automatically or require manual intervention, and whether they are attended or unattended.
-# '''Update Execution:''' During the update process, Cryptshare handles transitions to ensure continuity. If an update fails, the system automatically reverts to the previous stable version to maintain operational stability.
-# '''Notifications and Feedback:''' Administrators receive notifications about the update status. Alerts are provided for manual interventions and confirmations of successful updates. Notifications about non-critical issues are displayed only to administrators, ensuring they are informed of all pertinent details.
-# '''Restoration and Recovery:''' The system includes safeguards for automatic recoveries and can restore previous configurations if updates affect critical system components.
-This approach is designed to provide clarity and improve the manageability of the update process in Cryptshare.
+The update process is documented [[{{NAMESPACE}}:Updates|in this article.]]
 == 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.
+Administrators can now fully configure transfer policies by importing a CSV file. This update ensures that all settings available through the administration interface policy wizard are now configurable via CSV import. The CSV export now also contains all parameters that can be configured in the policy wizard. This enhancement simplifies e.g. the process of transferring fully configured policies from a test server to a production server.
 == 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.
+An issue has been resolved that caused (in rare cases) generated passwords to be rejected because they did not 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 ==
+== Discontinuation of "Legacy Archiving" connector ==
-With this release, legacy archiving functionality has been disabled by default to align with our transition towards file-based archiving solutions. It can now only be re-enabled through an advanced configuration property, ensuring that only users with specific needs access this feature. For details on enabling legacy archiving, please visit our [[CSSBackend en:Advanced Configuration|advanced configuration documentation]]. If legacy archiving is currently configured, you may need to reconfigure it during the update process. Information regarding this will be displayed during the update process, guiding administrators on how to transition to supported archiving methods.
+With this release, the outdated "Legacy Archiving" connector has been disabled by default to align with our transition towards the more modern and powerful "Local File System" archiving connector.
-== Additional Changes ==
+Before performing an update, you can check the menu "Transfer Processing" -> "Archiving" if there is a Legacy Archiving connector configured. More information about the archiving feature can be found [[{{NAMESPACE}}:Activating_the_Archiving_Feature|in this article]]. If legacy archiving is currently configured, please refer to the [[{{NAMESPACE}}:Migration of legacy archiving connector|migration guide from the Legacy Archiving to the Local File System archiving]]. In case, a Legacy Archiving connector is detected during the Post Update, a reminder hint message of the continuation will be presented in the Post Update screen.
-* '''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.
+== Network Patterns for Policy Rules ==
-* '''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.
+Policy configurations now support simultaneous IPv4 and IPv6 address inputs, applicable to both direct settings and CSV imports.  Previous issues with IPv6 compatibility have been resolved, ensuring all valid IPv6 addresses are now accepted. Additionally, an issue in the policy wizard regarding network matchers was resolved.
-* '''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.
+= Additional Changes =
+* Resolved an issue where downloaded log files might have been cached by the browser.
+* Resolved an issue that prevented sending of notifications during update check task.
-* '''Appliance Settings and Update Checks''': Fixed an error that occurred during appliance settings adjustments and refined the REST API to include sender notifications.
+* Resolved an error that occurred during appliance settings adjustments.
-* '''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.
+* Resolved an issue in the REST API where the sender notification flag was not applied correctly.
-* '''Library Upgrades''': Upgraded Java Runtime Environment (JRE) and Spring libraries to enhance performance and security.
+* Resolved an issue where large file names disrupted UI styling.
-* '''Admin UI Consistency''': Resolved inconsistencies where custom link settings were not properly reflected in the admin UI, ensuring a more reliable configuration experience.
+* Resolved an XSS issue in notification messages.
+* Resolved various issues with the administration of notification email subjects and signatures. They now require unique names, and can be detached from policy rules.
+* Resolved an issue where the order of Custom Links was not reflected in the configuration menu. Changes to Custom Links are now reflected directly in the Web App, without starting a new session.
+* Upgraded Java Runtime Environment (JRE) and Spring libraries.

CSSCurrent en:Version 7.0.0: Unterschied zwischen den Versionen