Hello Dominik,
I agree with you that the situation with tomb in stable is
not satisfactory.
Unfortunately the bug was detected to late to get the fix into buster
as buster was already in deep freeze at that time. So, in the end, the
release process led to the current situation.
> I use stable be
reached here with the same intention as Joerg Bornemann.
apparently it is against Debian philosophy to include a version that is
compatible with Debian 10 cryptsetup version. What document do I need to
read to understand the reasoning behind that?
I use stable because I expect the chance to thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Joerg,
thank you for your mail. The bug it is about is #930782 [1], and
fortunately there is a work-around:
> Locking the tomb specifying the valid cipher on the command line
works
>
>$ tomb lock -k x.key -o aes-xts-plain64 x.tomb
>
>[..
On Sun, 06 Oct 2019 22:43:32 +0200 Sven Geuer wrote:
Regarding 'important fix for usage of Tomb with cryptsetup 2.1':
This seems to refer to [2], 'Issue opening tombs with cryptsetup >
2.0', which is an annoying bug but not a security issue.
It would be merely an annoying bug if there was a w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: severity -1 wishlist
Regarding 'whitespace bug in KDF passwords':
This issue does not apply to Tomb 2.5 in Debian as it does not support
KDF passwords at all, see [1].
Regarding 'important fix for usage of Tomb with cryptsetup 2.1':
This s
Package: tomb
Version: 2.5+dfsg1-2
Severity: important
Version 2.6 of the Tomb provides an important fix for usage of Tomb
with cryptsetup 2.1 and future versions; it also fixes a whitespace
bug in KDF passwords that could drastically reduce the strength of
encryption. So, updating Tomb debian pa
6 matches
Mail list logo
