Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Milan Broz
On 4/12/24 9:11 AM, Jan Katins wrote: I snooped around in the source code a bit and found that libgcc_s seems to be dlopened and is special cased: https://salsa.debian.org/kernel-team/initramfs-tools/-/blob/master/hook-functions?ref_type=heads#L248-249 (original bugreport:

Bug#1032221: [pkg-cryptsetup-devel] Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

2023-03-07 Thread Milan Broz
Just FYI - I think that the whole problem can be avoided by merging this patch https://github.com/P-H-C/phc-winner-argon2/pull/331 (we have the patch applied in cryptsetup for embedded libargon already). Just upstream is no longer responding here... Milan

Bug#935702: [pkg-cryptsetup-devel] Bug#935702: Wrong DM device size due to integer truncation

2019-08-26 Thread Milan Broz
On 26/08/2019 08:03, Milan Broz wrote: > No need to report it upstream, I'll fix it. This is really stupid bug, all > sizes in code > must be uint_64t. I just wonder why no static analysis screamed here, I run > it on 32bit... Fixed here https://gitlab.com/cryptsetup/crypt

Bug#935702: [pkg-cryptsetup-devel] Bug#935702: Wrong DM device size due to integer truncation

2019-08-26 Thread Milan Broz
On 26/08/2019 03:28, Guilhem Moulin wrote: > On Sun, 25 Aug 2019 at 12:43:26 +, n...@waifu.club wrote: >> Not only the access to protected data is lost, the integritysetup's "open" >> operation actually succeeds. All reads on the incorrectly created DM device >> will of course fail with I/O

Bug#888072: volume-key FTBFS with cryptsetup 2:2.0.0-1

2018-01-24 Thread Milan Broz
The upstream patch (that is compatible with older libcryptsetup as well so can be applied globally) is here https://pagure.io/volume_key/c/ecef526a51c5a276681472fd6df239570c9ce518?branch=master Thanks, Milan

Bug#677127: relocation error

2012-06-12 Thread Milan Broz
On 06/11/2012 09:31 PM, p...@spth.de wrote: /sbin/crpytsetup: relocation error: /sbin/cryptsetup: symbol crypt_activate_by_key_file_offste, version CRYPTSETUP_1.0 not defined in file libcryptsetup.so.4 with link time reference just if it helps: crypt_activate_by_key_file_offset was added in

Bug#659235: cryptsetup: Fails to detect crypted devices on LVM

2012-02-09 Thread Milan Broz
On 02/09/2012 12:33 PM, Kai Weber wrote: Calling hook cryptroot cryptsetup: WARNING: failed to find deps for vg--sda-root cryptsetup: FAILURE: could not determine configuration for vg--sda-root The result of the warning/failure is a missing cryptroot file in initrd. Maybe a problem with

Bug#585378: cryptsetup: segfaults on boot (on powerpc)

2010-06-10 Thread Milan Broz
On 06/10/2010 12:43 AM, Mourad De Clerck wrote: cryptsetup asks the password for the root (luks) partition and proceeds to segfault. After which it asks the password again. Critical because it made this laptop unbootable. I repaired it with another powerpc laptop, target mode and chroot. It's