Your message dated Wed, 14 Aug 2019 19:52:54 +0200 with message-id <[email protected]> and subject line This bug has been fixed has caused the Debian Bug report #930782, regarding tomb: Invalid default cipher "aes-xts-plain64:sha256" 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 [email protected] immediately.) -- 930782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930782 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: tomb Version: 2.5+dfsg1-2 Severity: normal Tags: upstream Dear Maintainer, The default cipher is not accepted by cryptsetup any more. Locking a freshly digged tomb by $ tomb lock -k x.key x.tomb fails with [...] tomb [W] cryptsetup luksFormat returned an error. tomb [E] Operation aborted. According to https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt the default cipher "aes-xts-plain64:sha256" is not valid. ":sha256" only goes with "aes- cbc-essiv:sha256". The valid cipher would be "aes-xts-plain64". Locking the tomb specifying the valid cipher on the command line works $ tomb lock -k x.key -o aes-xts-plain64 x.tomb [...] tomb . Done locking x using Luks dm-crypt aes-xts-plain64 tomb (*) Your tomb is ready in x.tomb and secured with key x.key "aes-xts-plain64:sha256" should be corrected to "aes-xts-plain64" in /usr/bin/tomb and the manpage. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tomb depends on: ii cryptsetup-bin 2:2.1.0-5 ii e2fsprogs 1.44.5-1 ii gnupg 2.2.12-1 ii pinentry-gnome3 [pinentry] 1.1.0-2 ii sudo 1.8.27-1 ii zsh 5.7.1-1 tomb recommends no packages. tomb suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Source: tomb Version: 2.6+dfsg1-1 We believe that the bug you reported is fixed in the latest version of tomb, which is due to be installed in the Debian FTP archive. Regard, Sven -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEPfXoqkP8n9/QhvGVrfUO2vit1YUFAl1USnYACgkQrfUO2vit 1YUy+hAApW/3pOX6rtAp20ZwDLBzSICMNeataiWTTNJwfKv2VZO6XvaEOnl8gu4s h5jeUtHw2WarPSD9BNAlw+fbvZRvUEigUyCx8TcRrvaKEkb4WOe52jqw6Wh+EvWL XvMmGWjvDcOkbcPUmasFI4vcCC9pH6/KH7/PfMt6rt+/zkwvlvRiRHO8WB14uLWI j/77egnjoN6C+V/4fkJuNzfRGaUhE/5gKAkYAAQYU5RKIJSzH5tuPoVOY7szaunU XSEZtk5IT2xOMeTMjosZV6GmyM2fcytXzaEy+Yf7Fwl7ngBKP0gdQUcY4TqqVFwE Ec5/Ik4edr4JnNAeO+50HnbVUDa9Lt8iLpWbe4pqE0SBUsfhYCaQCVSNfsKPXesy K0UjSVkoNn0XVmpyXx9+Xwl+bu5v0KQcpbli6+kSeOvuLKx3sapxiv9nJYtL+4Jk CSEJ0m6nUb3YnZC4ugTjP3t/3y09cUDAFcQOdXPOLgjsnCX2ErKQMA5ckNvlyF2x KrtR4dHoI7mUWQ5kX+hNwVyGOZRZcnUVen0JWluavYv0ot0sOxgS091VImbIIM/O B4FpHKbuug3sXP8411eR1h+/ZQ9ynMEfh+p3gnJwR0sQv8Os5Pgjh1YK6KUWq7Qf Z+SbiJfsMhB3ul2n1mfO6xjVmf3SgXQUYN2qEX8qKUhjtnPyfwo= =z9Ub -----END PGP SIGNATURE-----
--- End Message ---
