Hello community,

here is the log from the commit of package cryptsetup for openSUSE:Factory 
checked in at 2019-02-20 14:08:36
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/cryptsetup (Old)
 and      /work/SRC/openSUSE:Factory/.cryptsetup.new.28833 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "cryptsetup"

Wed Feb 20 14:08:36 2019 rev:104 rq:677121 version:2.1.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/cryptsetup/cryptsetup.changes    2018-11-06 
15:25:56.220471801 +0100
+++ /work/SRC/openSUSE:Factory/.cryptsetup.new.28833/cryptsetup.changes 
2019-02-20 14:08:42.886991632 +0100
@@ -1,0 +2,33 @@
+Fri Feb 15 15:01:18 UTC 2019 - Jan Engelhardt <[email protected]>
+
+- Use noun phrase in summary.
+
+-------------------------------------------------------------------
+Fri Feb 15 09:41:52 UTC 2019 - [email protected]
+
+- New version 2.1.0
+  * The default size of the LUKS2 header is increased to 16 MB.
+    It includes metadata and the area used for binary keyslots;
+    it means that LUKS header backup is now 16MB in size.
+  * Cryptsetup now doubles LUKS default key size if XTS mode is used
+    (XTS mode uses two internal keys). This does not apply if key size
+    is explicitly specified on the command line and it does not apply
+    for the plain mode.
+    This fixes a confusion with AES and 256bit key in XTS mode where
+    code used AES128 and not AES256 as often expected.
+  * Default cryptographic backend used for LUKS header processing is now
+    OpenSSL. For years, OpenSSL provided better performance for PBKDF.
+
+  * The Python bindings are no longer supported and the code was removed
+    from cryptsetup distribution. Please use the libblockdev project
+    that already covers most of the libcryptsetup functionality
+    including LUKS2.
+  * Cryptsetup now allows using --offset option also for luksFormat.
+  * Cryptsetup now supports new refresh action (that is the alias for
+    "open --refresh").
+  * Integritysetup now supports mode with detached data device through
+    new --data-device option.
+- 2.1.0 would use LUKS2 as default, we stay with LUKS1 for now until
+  someone has time to evaluate the fallout from switching to LUKS2.
+
+-------------------------------------------------------------------

Old:
----
  cryptsetup-2.0.5.tar.sign
  cryptsetup-2.0.5.tar.xz

New:
----
  cryptsetup-2.1.0.tar.sign
  cryptsetup-2.1.0.tar.xz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ cryptsetup.spec ++++++
--- /var/tmp/diff_new_pack.z0wfhH/_old  2019-02-20 14:08:44.154991212 +0100
+++ /var/tmp/diff_new_pack.z0wfhH/_new  2019-02-20 14:08:44.154991212 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package cryptsetup
 #
-# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -12,7 +12,7 @@
 # license that conforms to the Open Source Definition (Version 1.9)
 # published by the Open Source Initiative.
 
-# Please submit bugfixes or comments via http://bugs.opensuse.org/
+# Please submit bugfixes or comments via https://bugs.opensuse.org/
 #
 
 
@@ -22,25 +22,25 @@
 %else
 Name:           cryptsetup
 %endif
-Version:        2.0.5
+Version:        2.1.0
 Release:        0
-Summary:        Set Up dm-crypt Based Encrypted Block Devices
+Summary:        Setup program for dm-crypt Based Encrypted Block Devices
 License:        SUSE-GPL-2.0-with-openssl-exception AND LGPL-2.0-or-later
 Group:          System/Base
 Url:            https://gitlab.com/cryptsetup/cryptsetup/
-Source0:        
https://www.kernel.org/pub/linux/utils/cryptsetup/v2.0/cryptsetup-%{version}.tar.xz
+Source0:        
https://www.kernel.org/pub/linux/utils/cryptsetup/v2.1/cryptsetup-%{version}.tar.xz
 # GPG signature of the uncompressed tarball.
-Source1:        
https://www.kernel.org/pub/linux/utils/cryptsetup/v2.0/cryptsetup-%{version}.tar.sign
+Source1:        
https://www.kernel.org/pub/linux/utils/cryptsetup/v2.1/cryptsetup-%{version}.tar.sign
 Source2:        baselibs.conf
 Source3:        cryptsetup.keyring
 BuildRequires:  device-mapper-devel
 BuildRequires:  fipscheck
 BuildRequires:  fipscheck-devel
-BuildRequires:  libgcrypt-devel
 BuildRequires:  libjson-c-devel
 BuildRequires:  libpwquality-devel
 BuildRequires:  libselinux-devel
 BuildRequires:  libuuid-devel
+BuildRequires:  pkgconfig(openssl)
 # 2.6.38 has the required if_alg.h
 BuildRequires:  linux-glibc-devel >= 2.6.38
 BuildRequires:  pkgconfig
@@ -64,7 +64,7 @@
 time via the config file %{_sysconfdir}/crypttab.
 
 %package -n libcryptsetup%{so_ver}
-Summary:        Set Up dm-crypt Based Encrypted Block Devices
+Summary:        Library for setting up dm-crypt Based Encrypted Block Devices
 Group:          System/Libraries
 Suggests:       libcryptsetup%{so_ver}-hmac
 
@@ -76,7 +76,7 @@
 time via the config file %{_sysconfdir}/crypttab.
 
 %package -n libcryptsetup%{so_ver}-hmac
-Summary:        Checksums for libcryptsetup4
+Summary:        Checksums for libcryptsetup%{so_ver}
 Group:          System/Base
 
 %description -n libcryptsetup%{so_ver}-hmac
@@ -84,7 +84,7 @@
 used for FIPS.
 
 %package -n lib%{name}-devel
-Summary:        Set Up dm-crypt Based Encrypted Block Devices
+Summary:        Header files for libcryptsetup
 Group:          Development/Libraries/C and C++
 Requires:       glibc-devel
 Requires:       libcryptsetup%{so_ver} = %{version}
@@ -118,6 +118,7 @@
   --enable-pwquality \
   --enable-gcrypt-pbkdf2 \
   --enable-libargon2 \
+  --with-default-luks-format=LUKS1 \
   --with-luks2-lock-path=/run/cryptsetup \
   --with-tmpfilesdir='%{_tmpfilesdir}'
 make %{?_smp_mflags} V=1

++++++ cryptsetup-2.0.5.tar.xz -> cryptsetup-2.1.0.tar.xz ++++++
/work/SRC/openSUSE:Factory/cryptsetup/cryptsetup-2.0.5.tar.xz 
/work/SRC/openSUSE:Factory/.cryptsetup.new.28833/cryptsetup-2.1.0.tar.xz 
differ: char 15, line 1


Reply via email to