Releases: Olf0/crypto-sdcard
Releases · Olf0/crypto-sdcard
v1.5.2-1.sfos220qcrypto
Re-release of v1.5.1-1.sfos220qcrypto
v1.5.2-1.sfos401regular
Change
Fix trying to deploy a file per rpm
, which was removed from the crypto-sdcard RPM per v1.5.1.
v1.5.1-1.sfos401regular
v1.5.1-1.sfos340regular
Changes
- Overhaul configuration files.
- Make the cryptography options for
cryptosd-plain@.service
configurable per configuration file(s). - Disable the
Requisite=dev-mapper-%i.device
in the mounting units (mount-cryptosd-*@.service
), because that is ensured by the calling udev rule when started automatically, but that statement prevented this unit from auto-starting its dependencies (needed to createdev-mapper-%i.device
in the first place) when started manually. - Let the mounting units (
mount-cryptosd-*@.service
) conflict withrescue.target
again, because starting them also startsudisks2.service
, which shall not be automatically triggered inrescue.target
. - Disable
IgnoreOnIsolate=true
in the unlocking units (cryptosd-*@.service
) for now. - Streamline instance string to only transport <UUID> (for LUKS) or <devname> (for "plain").
- Unlock and depend on /dev/disk/by-uuid/<UUID> (for LUKS) or /dev/<devname> (for "plain"), directly.
- Consequently omit creation of symlink /dev/crypto_luks_<UUID> (for LUKS) or /dev/crypto_plain_<devname> (for "plain").
- Use ENV{UDISKS_SYSTEM}="0" to let udisks2 treat the unlocked partition as user mountable (i.e., "not system", aka "removable"?!?).
v1.5.1-1.sfos340qcrypto
v1.5.1-1.sfos321regular
v1.5.1-1.sfos321qcrypto
v1.5.1-1.sfos220regular
v1.5.1-1.sfos220qcrypto
v1.5.0-1.sfos340regular
Changes
- Shorten journal output.
- Enhance documentation.
- Give udisksd a second to recognise the fresh device, before starting units dependent on an unlocking unit instance (
cryptosd-*@*.service
), i.e. the mounting units (mount-cryptosd-*@*.service
), which utiliseudisksctl mount
.