1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195
|
libblockdev (2.20-7+deb10u1) buster; urgency=medium
[ intrigeri ]
* Use existing cryptsetup API for changing keyslot passphrase.
Cherry-pick upstream fix to use existing cryptsetup API for atomically
changing a keyslot passphrase, instead of deleting the old keyslot
before adding the new one. This avoids data loss when attempting to
change the passphrase of a LUKS2 device via udisks2, e.g. from GNOME
Disks.
Deleting a keyslot and then adding one is risky: if anything goes wrong
before the new keyslot is successfully added, no usable keyslot is left
and the device cannot be unlocked anymore. There's little chances this
causes actual problems with LUKS1, but LUKS2 defaults to the memory-hard
Argon2 key derivation algorithm, which is implemented in cryptsetup with
the assumption that it runs as root with no MEMLOCK ulimit; this
assumption is wrong when run by udisks2.service under
LimitMEMLOCK=65536, which breaks adding the new keyslot, and makes us
hit the problematic situation (user data loss) every time.
With this change, changing a LUKS2 passphrase via udisks2 will still
fail in some cases, until the MEMLOCK ulimit problem is solved in
cryptsetup or workaround'ed in udisks2. But at least, if it fails, it
will fail _atomically_ and the original passphrase will still work.
(Closes: #928893)
-- Michael Biebl <biebl@debian.org> Sat, 20 Jul 2019 23:18:18 +0200
libblockdev (2.20-7) unstable; urgency=medium
* Cherry-pick Use-512bit-keys-in-LUKS-by-default.patch:
- Use AES-256 (512 bit key) by default. From 2.21. (Closes: #910249)
-- Jeremy Bicha <jbicha@debian.org> Tue, 05 Mar 2019 01:08:22 -0500
libblockdev (2.20-6) unstable; urgency=medium
* Don't build for non-Linux since kmod & other required deps are Linux-only
* Don't try to build nvdimm plugin on ia64 since ndctl hasn't built there yet
-- Jeremy Bicha <jbicha@debian.org> Sat, 01 Dec 2018 17:00:56 -0500
libblockdev (2.20-5) unstable; urgency=medium
* Try to build the crypto & nvdimm plugins only on architectures
where they will build
-- Jeremy Bicha <jbicha@debian.org> Mon, 26 Nov 2018 07:27:52 -0500
libblockdev (2.20-4) unstable; urgency=medium
* Team upload.
* Build the new NVDIMM plugin
* Bump debhelper compat to 11
-- Jeremy Bicha <jbicha@debian.org> Thu, 22 Nov 2018 08:18:22 -0500
libblockdev (2.20-3) unstable; urgency=medium
* Build the new VDO plugin
* debian/copyright: The upstream source is LGPL-2.1+ not GPL-2+
- Thanks Thorsten Alteholz for the careful ftpmaster review
-- Jeremy Bicha <jbicha@debian.org> Sat, 20 Oct 2018 20:15:54 -0400
libblockdev (2.20-2) unstable; urgency=medium
* Team upload.
* libblockdev2.symbols: Drop s390x specific stub symbols
* debian/rules: drop no longer needed removal of python2
* python3-blockdev: add python3-gi dependency (Closes: #896303)
-- Andreas Henriksson <andreas@fatal.se> Sat, 29 Sep 2018 12:56:11 +0200
libblockdev (2.20-1) unstable; urgency=medium
[ Andreas Henriksson ]
* New upstream release (LP: #1788374)
* Use new configure switch to disable python2
* Disable new nvdimm and vdo plugins for now
* Ship new dbus.h in libblockdev-utils-dev
* libblockdev2.symbols: drop internal _-prefixed symbols
* libblockdev2.symbols: Drop bd_.*_stub symbols
* libblockdev-kbd2.symbols: drop internal wait_for_file symbol
* Add newly introduced symbols
[ Jeremy Bicha ]
* Add lintian overrides for package-name-doesnt-match-sonames:
- Package names like libblockdev-lvm2 are more clear than libbd-lvm2
* Bump Standards-Version to 4.2.1
-- Jeremy Bicha <jbicha@debian.org> Fri, 28 Sep 2018 15:31:01 -0400
libblockdev (2.16-2) unstable; urgency=high
* debian/libblockdev2.symbols: Add s390x-specific symbols
-- Jeremy Bicha <jbicha@debian.org> Tue, 20 Feb 2018 07:44:30 -0500
libblockdev (2.16-1) unstable; urgency=medium
* Team upload
[ Jeremy Bicha ]
* New upstream release
* Add Multi-Arch: same to -dev packages, thanks multiarch hinter
* Add symbols files
* Update Vcs fields for migration to https://salsa.debian.org/
[ Andreas Henriksson ]
* Make libblockdev-fs2 depend on e2fsprogs (Closes: #887270)
-- Jeremy Bicha <jbicha@debian.org> Mon, 19 Feb 2018 19:15:55 -0500
libblockdev (2.14-3) unstable; urgency=medium
* Team upload
* Drop python-blockdev. It was a relatively new, unused Python 2 package.
-- Jeremy Bicha <jbicha@debian.org> Wed, 13 Dec 2017 09:29:43 -0500
libblockdev (2.14-2) unstable; urgency=medium
* Team upload
* Disable s390 plugin.
It's not used in Debian and causes a FTBFS on s390x due to uninstalled
files.
-- Michael Biebl <biebl@debian.org> Wed, 01 Nov 2017 14:32:01 +0100
libblockdev (2.14-1) unstable; urgency=medium
* Team upload
[ Andreas Henriksson ]
* Remove myself from uploaders
[ Michael Biebl ]
* New upstream version 2.14
* Fix watch file and upstream-vcs-tag
* Drop debian/patches/Drop-s390utils-vtoc.h-include-from-s390.api.patch,
merged upstream.
* Install new blockdev-utils.pc in libblockdev-utils-dev
* Bump Standards-Version to 4.1.1
-- Michael Biebl <biebl@debian.org> Wed, 01 Nov 2017 12:57:24 +0100
libblockdev (2.12-3) unstable; urgency=medium
* Team upload.
* Drop <s390utils/vtoc.h> include from s390.api.
This header is not available in Debian and as a result causes a FTBFS on
s390x. As it's not actually needed, simply remove the include.
(Closes: #872977)
-- Michael Biebl <biebl@debian.org> Tue, 12 Sep 2017 19:38:49 +0200
libblockdev (2.12-2) unstable; urgency=medium
* Fix gdisk dependency (Closes: #873748)
-- Andreas Henriksson <andreas@fatal.se> Thu, 31 Aug 2017 15:17:21 +0200
libblockdev (2.12-1) unstable; urgency=medium
* Replace btrfs-tools dependency with btrfs-progs (Closes: #873014)
* libblockdev-part2: Add sgdisk and fdisk dependencies
* libblockdev-dm2: Add dmsetup dependency
* libblockdev-lvm2: depend on thin-provisioning-tools
* Version some dependencies to match the code check
* New upstream release.
-- Andreas Henriksson <andreas@fatal.se> Wed, 30 Aug 2017 13:27:40 +0200
libblockdev (2.11-2) unstable; urgency=medium
* Clean out overzealous and wrong dependencies
-- Andreas Henriksson <andreas@fatal.se> Thu, 24 Aug 2017 14:06:53 +0200
libblockdev (2.11-1) unstable; urgency=medium
* New upstream release.
* Drop all debian patches, fixed upstream:
- debian/patches/add-gobject.patch
- debian/patches/add-libm.patch
- debian/patches/parted-fs-resize-pc-version.patch
* debian/rules: drop workaround using --exec-prefix configure argument.
* debian/libblockdev-utils-dev.install: ship new dev_utils.h
-- Andreas Henriksson <andreas@fatal.se> Thu, 24 Aug 2017 13:33:12 +0200
libblockdev (2.6-1) unstable; urgency=medium
* Initial release (Closes: #862776)
-- Andreas Henriksson <andreas@fatal.se> Thu, 17 Aug 2017 13:05:17 +0200
|