Hello community, here is the log from the commit of package cryptsetup for openSUSE:Factory checked in at 2020-04-05 20:49:04 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/cryptsetup (Old) and /work/SRC/openSUSE:Factory/.cryptsetup.new.3248 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "cryptsetup" Sun Apr 5 20:49:04 2020 rev:108 rq:790921 version:2.3.1 Changes: -------- --- /work/SRC/openSUSE:Factory/cryptsetup/cryptsetup.changes 2020-02-09 21:02:38.523361197 +0100 +++ /work/SRC/openSUSE:Factory/.cryptsetup.new.3248/cryptsetup.changes 2020-04-05 20:49:09.304930613 +0200 @@ -1,0 +2,33 @@ +Thu Apr 2 14:27:18 UTC 2020 - Ludwig Nussel <[email protected]> + +- 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. + +------------------------------------------------------------------- Old: ---- cryptsetup-2.3.0.tar.sign cryptsetup-2.3.0.tar.xz New: ---- cryptsetup-2.3.1.tar.sign cryptsetup-2.3.1.tar.xz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ cryptsetup.spec ++++++ --- /var/tmp/diff_new_pack.6ukHiO/_old 2020-04-05 20:49:10.160931432 +0200 +++ /var/tmp/diff_new_pack.6ukHiO/_new 2020-04-05 20:49:10.164931436 +0200 @@ -22,7 +22,7 @@ %else Name: cryptsetup %endif -Version: 2.3.0 +Version: 2.3.1 Release: 0 Summary: Setup program for dm-crypt Based Encrypted Block Devices License: SUSE-GPL-2.0-with-openssl-exception AND LGPL-2.0-or-later @@ -56,6 +56,8 @@ Requires(post): coreutils Requires(postun): coreutils +%lang_package(cryptsetup) + %description cryptsetup is used to conveniently set up dm-crypt based device-mapper targets. It allows to set up targets to read cryptoloop compatible @@ -166,7 +168,7 @@ %post -n libcryptsetup%{so_ver} -p /sbin/ldconfig %postun -n libcryptsetup%{so_ver} -p /sbin/ldconfig -%files -f %{name}.lang +%files %doc AUTHORS COPYING* FAQ README TODO docs/ChangeLog.old docs/*ReleaseNotes /sbin/cryptsetup%{?is_backports:2} %{_sbindir}/cryptsetup%{?is_backports:2} @@ -182,6 +184,8 @@ %ghost %dir /run/cryptsetup %endif +%files lang -f %{name}.lang + %files -n libcryptsetup%{so_ver} %{_libdir}/libcryptsetup.so.%{so_ver}* ++++++ cryptsetup-2.3.0.tar.xz -> cryptsetup-2.3.1.tar.xz ++++++ /work/SRC/openSUSE:Factory/cryptsetup/cryptsetup-2.3.0.tar.xz /work/SRC/openSUSE:Factory/.cryptsetup.new.3248/cryptsetup-2.3.1.tar.xz differ: char 15, line 1
