CSSCurrent en:Version 7.4.0: Unterschied zwischen den Versionen
(CSS-15496: Adding telemetry data.) |
Keine Bearbeitungszusammenfassung |
||
| (4 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt) | |||
| Zeile 1: | Zeile 1: | ||
Release Date: | Release Date: 26.08.2025 | ||
== Important Update Notes == | == Important Update Notes == | ||
| Zeile 13: | Zeile 13: | ||
The previous function “Common words are not allowed as passwords” has been renamed to “Passwords must not contain frequently used words (defined in words.lst)” to describe the function more accurately. | The previous function “Common words are not allowed as passwords” has been renamed to “Passwords must not contain frequently used words (defined in words.lst)” to describe the function more accurately. | ||
== Improvements == | == Improvements == | ||
* Obsolete log files and service definitions will be removed with this update, that were only relevant to earlier versions of Cryptshare and are no longer required. | * Obsolete log files and service definitions will be removed with this update, that were only relevant to earlier versions of Cryptshare and are no longer required. | ||
* The installed OWA package version displays the build number. | * The installed OWA package version displays the build number. | ||
* If the notification of all recipients fails during a transfer, the Cryptshare Server skips the notification of the sender about a ‘successful notification of the recipients’. Starting with this version, the sender's notification is now also saved as failed. This affects the display in the transfer log and responses from the SOAP and REST API. This is to avoid the false impression that the sender has been informed about the transfer. | * If the notification of all recipients fails during a transfer, the Cryptshare Server skips the notification of the sender about a ‘successful notification of the recipients’. Starting with this version, the sender's notification is now also saved as failed. This affects the display in the transfer log and responses from the SOAP and REST API. This is to avoid the false impression that the sender has been informed about the transfer. | ||
* The Java runtime environment has been updated to version 21.0.8. | * The Java runtime environment has been updated to version 21.0.8. | ||
=== Restructured Transfer Options Screen === | |||
The transfer options screen was restructured to allow users to focus on the most important transfer options. The other options are now hidden by default and can be opened by the users themselves. | |||
=== Content Security Policy changes === | === Content Security Policy changes === | ||
| Zeile 42: | Zeile 42: | ||
In order to check which data is sent to Pointsharp, you can download this support package yourself in the administration interface. | In order to check which data is sent to Pointsharp, you can download this support package yourself in the administration interface. | ||
=== Extended Telemetry === | |||
In order to better understand how Cryptshare is used, the [[{{NAMESPACE}}:Telemetry|Telemetry]] data has been extended. More details can be found on the respective page. | |||
== Bug Fixes == | == Bug Fixes == | ||
Aktuelle Version vom 27. August 2025, 06:52 Uhr
Release Date: 26.08.2025
Important Update Notes
Language Packages
In case your language packages have been modified, the attached delta-file Datei:Delta english lp 7.3.0 to 7.4.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.
New features
Improved password security by checking against "commonly used passwords"
When defining password security, it is now possible to prohibit the use of passwords that are among the 10,000 most commonly used passwords on the Internet. For configuration instructions, see the article on Password Policy.
The previous function “Common words are not allowed as passwords” has been renamed to “Passwords must not contain frequently used words (defined in words.lst)” to describe the function more accurately.
Improvements
- Obsolete log files and service definitions will be removed with this update, that were only relevant to earlier versions of Cryptshare and are no longer required.
- The installed OWA package version displays the build number.
- If the notification of all recipients fails during a transfer, the Cryptshare Server skips the notification of the sender about a ‘successful notification of the recipients’. Starting with this version, the sender's notification is now also saved as failed. This affects the display in the transfer log and responses from the SOAP and REST API. This is to avoid the false impression that the sender has been informed about the transfer.
- The Java runtime environment has been updated to version 21.0.8.
Restructured Transfer Options Screen
The transfer options screen was restructured to allow users to focus on the most important transfer options. The other options are now hidden by default and can be opened by the users themselves.
Content Security Policy changes
The default Content Security Policy (CSP) configuration of the Cryptshare Web App (end user interface) and Cryptshare Admin Interface has been tightened and no longer allows unsafe-inline or unsafe-eval directives.
The CSP configuration has also been tightened in case additional resources from other sources are used by removing the previously mentioned directives. If you only integrate images from other sources, no further adjustment is required.
REST-API
Enhanced Transfer Polling: Sender Details now available
The sender’s name and phone number are now saved in the database and can be retrieved via the Sender/Recipient Transfer polling API.
Server Status Endpoint (REST API Version)
The Cryptshare REST API now offers a endpoint to query which REST API version is available on this Cryptshare Server. In case you are working with multiple Cryptshare servers, you can now use multiple feature sets based on the respective REST APIs.
The built-in Cryptshare support feature was extended. Besides the log files, the support package that is sent to Pointsharp will now additionally contain the policy configuration, the configured file type filters, the cryptshare.properties and launcher.ini files. This allows our support team to check the policy and file type filter configuration in case of requests regarding the configuration of the Cryptshare Server.
In order to check which data is sent to Pointsharp, you can download this support package yourself in the administration interface.
Extended Telemetry
In order to better understand how Cryptshare is used, the Telemetry data has been extended. More details can be found on the respective page.
Bug Fixes
- Fixed an issue causing application logs to appear in host system syslogs (`/var/log/messages` or `/var/log/syslog`).
- Fixed an issue where boolean properties in the Transfer-Polling API response defaulted to
falsewhen not included. They now returnnullunless specified via the Fields parameter. - Fixed an issue where the Transfers in the "Processing" state that exceeded their
expiration_datewere incorrectly returned as active in the API response before the cleanup task ran. They are now correctly returned with the stateDELETED_BY_EXPIRATION - Fixed an issue where under specific circumstances the "Save changes" button in the policy administration was not responsible.
- Fixed an issue that prevented transfers created by QUICK from being polled via the Rest Api.
- Fixed an issue of log export showing subject and messages even when logging is deactivated.