Your message dated Tue, 04 Feb 2020 15:04:29 +0000
with message-id <e1iyzkb-00024a...@fasolo.debian.org>
and subject line Bug#950628: fixed in cryptsetup 2:2.2.2-3
has caused the Debian Bug report #950628,
regarding cryptsetup-initramfs: can't unlock argon2 keyslots: incompatible with
libgcc1 1:10-20200202-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
950628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup-initramfs
Version: 2:2.2.2-2
Severity: critical
The side effect of initramfs logic used to find libgcc leads to
unbootable system if libgcc is in different location than libc. Maybe
something like "ldconfig -p | grep libgcc_s.so.1" should be used to
locate libgcc instead?
Details:
The recent update of libgcc1 to version 1:10-20200202-1 (unstable) moved
it from:
/lib/x86_64-linux-gnu/libgcc_s.so.1
to:
/lib/libgcc_s.so.1
The initramfs hook for cryptsetup is still looking for it using previous
location based on libc:
# cat /usr/share/initramfs-tools/hooks/cryptroot
[...]
LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')"
find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read
so; do
copy_exec "$so"
done
# echo $(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')
/lib/x86_64-linux-gnu
# ldd /sbin/cryptsetup
[...]
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4b0b6c0000)
This leads to omission of libgcc_s.so.1 in initramfs and makes unlocking
the root drive impossible (in case of LUKS2 at least) because of the
following error:
libgcc_s.so.1 must be installed for pthread_cancel to work
I created initramfs hook in /etc/ that includes libgcc and it solves the
problem (obviously as workaround):
cp /lib/libgcc_s.so.1 "${DESTDIR}/usr/lib/"
The difference in libgcc1 packages:
(version 1:10-20200202-1)
# dpkg -L libgcc1
/.
/lib
/lib/libgcc_s.so.1
/lib/x86_64-linux-gnu
/usr
/usr/share
/usr/share/doc
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libgcc1
/usr/share/doc/libgcc1
(version 1:9.2.1-25)
# dpkg -L libgcc1
/.
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/libgcc_s.so.1
/usr
/usr/share
/usr/share/doc
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libgcc1
/usr/share/doc/libgcc1
Thanks,
Karol
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.2.2-3
We believe that the bug you reported is fixed in the latest version of
cryptsetup, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guilhem Moulin <guil...@debian.org> (supplier of updated cryptsetup package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 04 Feb 2020 14:11:12 +0100
Source: cryptsetup
Architecture: source
Version: 2:2.2.2-3
Distribution: unstable
Urgency: high
Maintainer: Debian Cryptsetup Team
<pkg-cryptsetup-de...@alioth-lists.debian.net>
Changed-By: Guilhem Moulin <guil...@debian.org>
Closes: 939766 950628
Changes:
cryptsetup (2:2.2.2-3) unstable; urgency=high
.
* initramfs hook: Workaround fix for the libgcc_s's source location.
(Closes: #950628, #939766.) See #950254 for the proper fix.
Checksums-Sha1:
6bd7a7e6ba24d977ac565cf74a2f3f4449193e06 2853 cryptsetup_2.2.2-3.dsc
e7725801be13e865dece73f159a51b0da43f5df9 112644
cryptsetup_2.2.2-3.debian.tar.xz
e1fdc125342a250480383be6a3770192c9aa0bd9 9583
cryptsetup_2.2.2-3_amd64.buildinfo
Checksums-Sha256:
8c7b444bfc4ae0af1276eb7518925cde8646136297ea92f964e877f6dc7dfa04 2853
cryptsetup_2.2.2-3.dsc
56295914d8d03a4d3a35b53cb8396234b0fc0ec83705afa112e6789d3e8c26ca 112644
cryptsetup_2.2.2-3.debian.tar.xz
3849f212716aeb9b39bbb16c9a9852553a0bd9e6dea390701f8ef0279e483f32 9583
cryptsetup_2.2.2-3_amd64.buildinfo
Files:
bb05b359202e996ab652e7afc7283a3f 2853 admin optional cryptsetup_2.2.2-3.dsc
ef62099e3d2ac07cf768f8d5a317eaf3 112644 admin optional
cryptsetup_2.2.2-3.debian.tar.xz
362ea373ae35913a0c2aa6cc8c22e4f7 9583 admin optional
cryptsetup_2.2.2-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAl45ciIACgkQ05pJnDwh
pVKh8w//fLKccINCkbS9T+RiSLfAo8ToSYnyg2bM93nux9EHq9AYKgFcvIjw1EDf
m0IeaubRZn81rVw/b+LMsIkQ4ZMkZqI5YNb398xExUrQi+rdvdXUP+LXno4c06bM
RG8I3MKTm+iB4tbHhP1bVYyGOMqv0Z+xLVuDJHwczaim9XNVwpDM+S2ItwB/B1dm
/2fZaqgD/BQ6uyoxOSpLSH2Z5ojbcO1ojtsLNQpDjxi7A2H54V7jkRZGXXLtITAB
Wst+3qjmyjv/7H1Ym9IQmhOt7oYjqkSCEABADSHFkDxFPp78QwWH58loJb9ibLyy
NGU1jH0E9zD5deP/5F8yPpl8yRAia1ehkNc+8PbrXL8XJu9AEJZOkflpTLouQneE
JDOZSUD96zqZTi+WhJKQfiwVnOiIqRYqcqzJWDFgpyhCm5oMvhce7cRIrp4yWpqc
KHuoPYsZ7N8KJz0nlMQx+jnitQQBOFmrzYX/NEiOhvPl5sDpx5ABKGSrTsScHgnZ
cU2hnKfu3/OKgaZyqZPGhixsppZyGaUKj56g3iwhJ8W6dBv608hS0sQmRKn/Yaf7
lAbaF1UBtNDOUrSLWJaAEq4QjHiCprkZ2ilUwYj2Ph5mLANcDbuyirPIUzjZ+L7V
7poRaTNrZHiwwYJO0UUa9+tbVPZTKx2hjoJWmgHfYnagrzF90d0=
=cHwt
-----END PGP SIGNATURE-----
--- End Message ---
