CSSCurrent en:Version 7.7.0
Release Date: 08.05.2026
Important Update Notes
Language Packages
In case your language packages have been modified, the attached delta-file Datei:Delta english lp 7.6.0 to 7.7.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
This Cryptshare version allows an upgrade of the underlying operating system. After the update to Cryptshare version 7.7.0 is complete, the Cryptshare administration interface provides the option to start the upgrade process.
The upgrade to 16.0 has some specific information, the Cryptshare administrator should be aware of. Please read the documentation -
Upgrading the distribution from openSUSE Leap 15.6 to 16.0Introduction of SFTP Archiving (Deprecation Notice of the Secure Copy (SCP) Archiving)
Secure Copy (SCP) archiving has been deprecated and will be removed in a future release of Cryptshare Server. Users are required to migrate to Secure File Transfer (SFTP) archiving prior to that release. SFTP archiving offers the same configuration options as SCP and can be configured under Transfer Processing → Archiving. The Test connection function verifies that the SFTP subsystem is enabled on the remote host. Once SFTP archiving has been configured and verified, any existing SCP archiving configuration must be removed.
Improvements
Increased usability by showing required fields and more explanations in the Web App
For users that are unfamiliar with the Cryptshare Web App, the usability was improved:
- Visible markers now highlight all fields that need required input.
- New explanations were added to the transfer workflow, explaining what has to be done on a page and why it is necessary.
Usage of newest product names
In the admin interface, all add-in product related texts were updated to reflect all new product names of the Cryptshare product line that were changed in the previous months:
- Cryptshare for Notes is now known as Cryptshare for Notes and Domino
- Cryptshare for Outlook is now known as Cryptshare for Outlook (Classic)
- Cryptshare for OWA is now known as Cryptshare for Outlook
Use of additional security headers
From this version onwards, new security headers are set by default for requests:
- Cross-Origin-Embedder-Policy: credentialless
- Cross-Origin-Resource-Policy: same-origin
- Permissions-Policy: geolocation=(), camera=(), microphone=(), payment=(), usb=(), midi=(), accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), encrypted-media=(), gyroscope=(), magnetometer=(), picture-in-picture=(), speaker-selection=(), sync-xhr=(), vr= ()
- X-Permitted-Cross-Domain-Policies: none
- Cross-Origin-Opener-Policy: same-origin-allow-popups
If necessary, these headers can be deactivated again or set to different values. Please note that tightening the header values may result in a loss of functionality. Further information can be found here.
Additional improvements
- The accessibility of status boxes was improved with new icons and added descriptive labels to ensure information is communicated through more than just color.
- In order to better understand if and with which protocol Microsoft Exchange 365 is used, the Telemetry data has been extended. More details can be found on the respective page.
- Upgraded the Spring library to version 7.
- Several included third-party components have been updated.
Bug Fixes
- An issue was resolved where a lot of unnecessary log messages regarding ReleaseInfo were written into the log files.
- An issue was resolved where, when using the file type filter, temporary files were not deleted correctly.
- An issue was resolved where messages sent via Cryptshare for Outlook were not displayed correctly at the recipient and that produced warning messages in the server log.
- An issue was resolved where the Cryptshare service was restarted while a Cryptshare update was in progress.
- An issue was resolved where line breaks were not correctly displayed in the resulting notification email and in the preview.
- An issue was resolved where QUICK transfers were sometimes not included in the usage data.