CSSCurrent en:Version 7.2.1

Aus Cryptshare Documentation
Version vom 12. Mai 2025, 09:48 Uhr von imported>Edayans (Adding warning about two services)
(Unterschied) ← Nächstältere Version | Aktuelle Version (Unterschied) | Nächstjüngere Version → (Unterschied)
Wechseln zu:Navigation, Suche

Release Date: 08.04.2025

Important Update Notes

launcher.ini

This section only applies to systems that have been updated from version 7.2.0 to 7.2.1. If you have updated from version 7.1.0 to 7.2.1, this section is not relevant.

After updating from 7.2.0 to 7.2.1, please check whether the contents of the launcher.ini file are correct, for example the specification of proxy settings or the definition of the directory for temporary files. If your customisations are no longer available, you can find a backup of this file in the backup that was created when you updated to version 7.2.0.

Post-Migration cleanup: Disabling legacy init.d service

After migrating application service management from legacy init.d scripts to modern systemd units (systemctl) across openSUSE and other Linux distributions, both service definitions have been retained for backward compatibility and rollback purposes. However, running both simultaneously can cause conflicts or unexpected behavior. If you detect both services running, follow these steps to ensure only the systemd service is active:

  1. Verify the new systemd service definition exists:
    • On openSUSE, check for /usr/lib/systemd/system/cryptshare.service
    • On other Linux distributions, check for /etc/systemd/system/cryptshare.service
  2. Back up the old init.d service script (for potential rollback to cryptshare 7.1.0 or older)
    1. sudo cp /etc/init.d/cryptshare ./cryptshare-old-service
  3. Remove the legacy init.d service definition:
    • Delete the old service script:
      sudo rm /etc/init.d/cryptshare
    • Reload systemd to apply changes:
      sudo systemctl daemon-reload

After completing these steps, only the systemd-managed service will control the application.

Improvements

  • Upgraded Spring version to 6.2.5 to address security vulnerabilities.
  • Emails sent to support will have specific subject tag line for identifying them as support request.

Bug Fixes

  • Resolved an issue during the update procedure leading to VM parameters to be lost.