Control: tag -1 - moreinfo
Control: found -1 + 2:2.3.4-2
Hi,
I am sorry for the misleading guesses from my previous messages.
I finally got to running some more tests and it is not a 32bit or arm
problem.
Long-keyed volumes created by 2.0.2 cannot be opened by 2.2.2 and vice
versa.
I tested
Package: linux-image-armmp
Version: 5.9.15-1
Dear Maintainer,
since upgrading to the 5.9.0-x-armmp armhf kernels I am seeing
processes getting getting randomly stuck in D-state.
I observed this issue with 5.9.0-1-armmp and 5.9.0-4-armmp.
I did not observe the issue with 5.8.0-3-armmp or any
Dear Maintainer,
I ran into this when upgrading from stretch to buster during 2020/21
hollidays,
which means I was definitely running d-s-s 1:9+2020.12.04 from
buster-security.
The system was low on RAM and both /tmp and swap were backed by a slow
SD card.
This is caused by
notfound 972950 11.1.2+b1
Package: ntpdate
Version: 1:4.2.8p12+dfsg-4
Severity: wishlist
Tags: patch
Dear Maintainer,
the current behavior of nptdate is sub-optimal when it is run on a mix
of DNS names and IP addresses and the DNS resolver performs DNSSEC
validation.
I propose two alternative solutions to handle DNS
Package: debian-goodies
Version: 0.87
Severity: wishlist
Dear Maintainer,
checkrestart ships with a list of exclusions that cannot be overriden.
I believe many of those are unwarranted and would like to remove them.
The exclusion list can be appended using the '-i' flag.
I propose implementing
Dear Maintainer,
I have also been harmed by this regression in 'ncal' binary.
This feature was removed in #904839 due to compatibility concerns.
All systems I used in the last 5 years highlighted the current day,
so I believe those compatibility concerns are very questionable.
Also #833226,
Hi,
I won't be able to help debugging this as I don't have a >2TiB disk
around. (Could fake the size and format with --no-wipe, but ...
I recall integrity checks failing on all sectors. It should be enough
to format only a part of the device with 32-bit 2:2.0.
e.g.
prepare# head -c 4096
clarification: I am testing it with a volume I created and used with
cryptsetup 2:2.0. With 2:2.1 and 2:2.2 integritysetup-open seems to
succeed, but the embedded ext4 filesystem cannot be used. Attempt to
read the superblock raise I/O errors due to integrity mismatches.
Best,
n.b.f.
Package: cryptsetup-bin
Version: 2:2.1.0-5+deb10u2
Severity: important
Dear Maintainers,
this is an unfortunate folowup to #935702. I thank Milan Broz very much
for fixing that one so quickly.
Unfortunately, even though the mapped size is now correct,
integritysetup still silently
Package: cryptsetup-bin
Version: 2:2.1.0-5
Severity: serious
Dear Maintainer,
cryptsetup in Stable contains multiple severe integer handling issues.
Created DM device's size is set incorrectly due to integer truncation.
Not only the access to protected data is lost, the integritysetup's
11 matches
Mail list logo
