v1.4.0-1.sfos340regular

Changes:

• Cease to sleep for a second before calling udisksctl mount should be feasible now on all devices (i.e., also fast ones) due to more, more precise and more robust dependency definitions.
• Cease to wait for udev-settle.service, because using it is not recommended by its documentation (but just prolongs boot time, while providing a huge safety margin), plus the crypto-*@.service files and their calling rules in 96-cryptosd.rules now should fulfill the prerequisites for dropping it.
  Furthermore it seems to need an additional Wants=udev-settle.service to work, hence crypto-sdcard propably never really waited for After=udev-settle.service anyway.
• Cease to (un)set ENV{SYSTEMD_USER_WANTS}="", because this was introduced as a safety measure long ago: Before the release of SailfishOS 3.0.0 it was unclear to me, if Jolla may rely on a User Unit started here for the manual unlocking of encrypted (partitions on) SD-Cards at the GUI. This turned out not to be feasible by a User Unit, because it appears to be impossible to collect the necessary information within a user unit, and the information for which user (rsp., in which user's context) to start a User Unit at Systemd level (Jolla's udisksctl-user script solves that, and needs root context to work).
  Plus, AFAICS no udev rule deployed by SailfishOS ever started a User Unit per ENV{SYSTEMD_USER_WANTS}="" (see grep -ro 'ENV[{]SYSTEMD_U.*[}]=".*"' /{etc,lib}/udev/rules.d | sort -u).
• Drop superfluous MODE="0660" and GROUP="disk" from 96-cryptosd.rules: These are the default values for all block devices!
• Hard-quote argument string for ENV{SYSTEMD_WANTS=""} to make crypto-sdcard work on SailfishOS 4.0.1 "Koli".
• Documentation enhancements
• Reflect the consolidation of multiple changes accumulated throughout the v1.3.x releases of crypto-sdcard and the "cleanup" in this release by increasing its minor version number.

v1.4.0-1.sfos340qcrypto

See release notes for v1.4.0-1.sfos340regular.

v1.4.0-1.sfos321regular

See release notes for v1.4.0-1.sfos340regular.

v1.4.0-1.sfos321qcrypto

See release notes for v1.4.0-1.sfos340regular.

v1.3.4-1.sfos340regular

Changes

• Adopt changes from mount-sdcard 1.3.4.
• Try to make 96-cryptosd.rules more robust, which may be sufficient to stablilise crypto-sdcard on SailfishOS 4.0.1.
• Try to enhance the parsing of "key"-files in "plain" mode.
  This change requires to convert extant "key"-files for "plain" mode, see details.
  New "plain" partitions shall be created slightly differently now, in order to take advantage of this enhancement.
  Note that this enhancement of the "plain" mode is untested, because I do not use "plain" (i.e., non-LUKS) partitions, thus its status is currently "experimental".

v1.3.4-1.sfos340qcrypto

See release notes for v1.3.4-1.sfos340regular.

v1.3.4-1.sfos321regular

See release notes for v1.3.4-1.sfos340regular.

v1.3.4-1.sfos321qcrypto

See release notes for v1.3.4-1.sfos340regular.

v1.3.3-1.sfos340regular

Changes

• Remove conflict to rescue.target for having this available at the recovery console.
• Adopt changes from mount-sdcard 1.3.3.
• Adapt changes in mount-sdcard 1.3.2 to crypto-sdcard:
  The Systemd EnvironmentFiles mount-cryptosd-luks.conf and mount-cryptosd-luks@crypto_luks_<UUID>.conf (in this order), respectively mount-cryptosd-plain.conf and mount-cryptosd-plain@crypto_plain_<device-name>.conf, in /var/lib/environment/udisks2/ are evaluated for additional mount options, if they exist (one or both).
  Take a look at ls /dev/mapper/crypto* for the partition specific part (between the @ and the .conf extension) of the file names for the partition specific configuration files.
  These configuration files can be created by a system administrator (i.e., you), so if you want to add restricting mount options, see here for details.

Note that this release does not contain a fix for the breakage SailfishOS 4.0.1 brought. This release contains changes queued up earlier, some of which are supposed to make the startup and shutdown behaviour more robust, which may ease debugging that.

v1.3.3-1.sfos340qcrypto

See release notes for v1.3.3-1.sfos340regular.