Set Up dm-crypt Based Encrypted Block Devices

Edit Package cryptsetup

cryptsetup is used to conveniently set up dm-crypt based device-mapper
targets. It allows to set up targets to read cryptoloop compatible
volumes as well as LUKS formatted ones. The package additionally
includes support for automatically setting up encrypted volumes at boot
time via the config file /etc/crypttab.

Refresh
Refresh
Source Files
Filename Size Changed
baselibs.conf 0000000037 37 Bytes
cryptsetup-2.3.1.tar.sign 0000000833 833 Bytes
cryptsetup-2.3.1.tar.xz 0011041592 10.5 MB
cryptsetup.changes 0000068823 67.2 KB
cryptsetup.keyring 0000003284 3.21 KB
cryptsetup.spec 0000006702 6.54 KB
Revision 108 (latest revision is 127)
Dominique Leuenberger's avatar Dominique Leuenberger (dimstar_suse) accepted request 790921 from Ludwig Nussel's avatar Ludwig Nussel (lnussel) (revision 108)
- Split translations to -lang package
- New version to 2.3.1
  * Support VeraCrypt 128 bytes passwords.
    VeraCrypt now allows passwords of maximal length 128 bytes
    (compared to legacy TrueCrypt where it was limited by 64 bytes).
  * Strip extra newline from BitLocker recovery keys
    There might be a trailing newline added by the text editor when
    the recovery passphrase was passed using the --key-file option.
  * Detect separate libiconv library.
    It should fix compilation issues on distributions with iconv
    implemented in a separate library.
  * Various fixes and workarounds to build on old Linux distributions.
  * Split lines with hexadecimal digest printing for large key-sizes.
  * Do not wipe the device with no integrity profile.
    With --integrity none we performed useless full device wipe.
  * Workaround for dm-integrity kernel table bug.
    Some kernels show an invalid dm-integrity mapping table
    if superblock contains the "recalculate" bit. This causes
    integritysetup to not recognize the dm-integrity device.
    Integritysetup now specifies kernel options such a way that
    even on unpatched kernels mapping table is correct.
  * Print error message if LUKS1 keyslot cannot be processed.
    If the crypto backend is missing support for hash algorithms
    used in PBKDF2, the error message was not visible.
  * Properly align LUKS2 keyslots area on conversion.
    If the LUKS1 payload offset (data offset) is not aligned
    to 4 KiB boundary, new LUKS2 keyslots area in now aligned properly.
  * Validate LUKS2 earlier on conversion to not corrupt the device
    if binary keyslots areas metadata are not correct.
Comments 0
openSUSE Build Service is sponsored by