Device-Mapper Crypto

• Thread Index

• Re: Two questions
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Two questions
  • From: mgreger@xxxxxxxxxxxx
• Re: Two questions
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Two questions
  • From: mgreger@xxxxxxxxxxxx
• [PATCH] cryptsetup: add support for the "fix_padding" option
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• Re: LUKS + HSM
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• LUKS + HSM
  • From: "FERON, Laurent (SOGETI REGIONS SAS)" <laurent.feron.external@xxxxxxxxxx>
• Re: Question regarding Cryptosetup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Question regarding Cryptosetup
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Question regarding Cryptosetup
  • From: Petar Zdravkov <p.zdravkov1617@xxxxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• [ANNOUNCE] cryptsetup 2.2.2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Does ver. 1.7.5 support veracrypt with PIM?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Does ver. 1.7.5 support veracrypt with PIM?
  • From: netmonitoring <netmonitoring@xxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• Mastery Key and RAM burn-in
  • From: "procmem@xxxxxxxxxx" <procmem@xxxxxxxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Philipp Rösch <philipp@xxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: Mastery Key and RAM burn-in
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Mastery Key and RAM burn-in
  • From: "procmem@xxxxxxxxxx" <procmem@xxxxxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Philipp Rösch <philipp@xxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Philipp Rösch <philipp@xxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Philipp Rösch <philipp@xxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Anyone know why I can't access my volumes?
  • From: Philipp Rösch <philipp@xxxxx>
• Re: 10 M Luks2 header size?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: Command failed with code -1 (wrong or missing parameters)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 10 M Luks2 header size?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Command failed with code -1 (wrong or missing parameters)
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• 10 M Luks2 header size?
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• question on LUKS2
  • From: Hualing Yu <hualing.yu@xxxxxxx>
• Re: Moving LUKS-LVM partition with KDE Partition Manager broke it
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Moving LUKS-LVM partition with KDE Partition Manager broke it
  • From: Hijack Eel <hijackeel@xxxxxxxxx>
• Re: Reencrypt process questions
  • From: Yexie2Fe <yexie2Fe@xxxxxxxxxxxxx>
• Re: Reencrypt process questions
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Reencrypt process questions
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Reencrypt process questions
  • From: Yexie2Fe <yexie2Fe@xxxxxxxxxxxxx>
• Re: problem with cryptsetup 2.21 - compiled OK but now getting version error
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• problem with cryptsetup 2.21 - compiled OK but now getting version error
  • From: John Williamson <tyringham@xxxxxxxxx>
• Re: Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Why is it necessary to "wipe" an authenticated luks2 device when creating it?
  • From: ".. ink .." <mhogomchungu@xxxxxxxxx>
• Re: Building issues with latest cryptsetup package
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Building issues with latest cryptsetup package
  • From: Anon <5050202089@xxxxx>
• [ANNOUNCE] cryptsetup 2.2.1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Bindings to other programming languages (Golang)
  • From: Martin Jungblut <martinjungblut@xxxxxxxxx>
• Re: Bindings to other programming languages (Golang)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Bindings to other programming languages (Golang)
  • From: Martin Jungblut <martinjungblut@xxxxxxxxx>
• Re: Integration with Active Directory
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Integration with Active Directory
  • From: Bruno <brunosantos.pr@xxxxxxxxx>
• Re: Device ... is still in use.
  • From: Jean-Paul Calderone <exarkun@xxxxxxxxxxxxxxxxx>
• Re: Device ... is still in use.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Device ... is still in use.
  • From: Jean-Paul Calderone <exarkun@xxxxxxxxxxxxxxxxx>
• Re: Device ... is still in use.
  • From: Jean-Paul Calderone <exarkun@xxxxxxxxxxxxxxxxx>
• Re: Device ... is still in use.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Device ... is still in use.
  • From: Jean-Paul Calderone <exarkun@xxxxxxxxxxxxxxxxx>
• Re: Device ... is still in use.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Device ... is still in use.
  • From: Jean-Paul Calderone <exarkun@xxxxxxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.2.0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS Header crruption
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS Header crruption
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: LUKS Header crruption
  • From: "Konstantin V. Gavrilenko" <k.gavrilenko@xxxxxxxxxx>
• Re: LUKS Header crruption
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS Header crruption
  • From: Uwe Menges <uwe.menges@xxxxxx>
• Re: LUKS Header crruption
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• LUKS Header crruption
  • From: "Konstantin V. Gavrilenko" <k.gavrilenko@xxxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Tom Eccles <tom.eccles@xxxxxxxxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Tom Eccles <tom.eccles@xxxxxxxxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Tom Eccles <tom.eccles@xxxxxxxxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Tom Eccles <tom.eccles@xxxxxxxxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Tom Eccles <tom.eccles@xxxxxxxxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Tom Eccles <tom.eccles@xxxxxxxxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: veritysetup forward error correction failure
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• veritysetup forward error correction failure
  • From: Tom Eccles <tom.eccles@xxxxxxxxxxxxxxx>
• Re: Support for plain mode in cryptsetup
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Support for plain mode in cryptsetup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Support for plain mode in cryptsetup
  • From: Maksim Fomin <maxim@xxxxxxxxx>
• Re: LUKS2 auth.encryption - do not use MORUS cipher
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS2 auth.encryption - do not use MORUS cipher
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Re: LUKS2 auth.encryption - do not use MORUS cipher
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: LUKS2 auth.encryption - do not use MORUS cipher
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS2 auth.encryption - do not use MORUS cipher
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• LUKS2 auth.encryption - do not use MORUS cipher
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Doubt on string
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Doubt on string
  • From: Rafael Fontenelle <rafaelff@xxxxxxxxx>
• Automatically construct LUKS header out of several dynamically prepared key slots?
  • From: Ignat Insarov <kindaro@xxxxxxxxx>
• Maximum useful size of keyfile
  • From: V V <vakevk@xxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.2.0-rc1 (experimental)
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Re: Export status for cryptsetup (1.7.5)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.2.0-rc1 (experimental)
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Export status for cryptsetup (1.7.5)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Export status for cryptsetup (1.7.5)
  • From: contact-oss-cct <contact-oss.cct@xxxxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.2.0-rc1 (experimental)
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.2.0-rc1 (experimental)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: Simulating Corruption
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Simulating Corruption
  • From: Robby Nelson <robertb.nelson@xxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: Dm-integrity freeze
  • From: Hans van Kranenburg <hans@xxxxxxxxxxx>
• Re: Dm-integrity freeze
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] Dm-integrity freeze
  • From: Hans van Kranenburg <hans@xxxxxxxxxxx>
• Re: dm-integrity and bcache
  • From: Robby Nelson <robertb.nelson@xxxxxxxxx>
• Re: [dm-devel] Dm-integrity freeze
  • From: Hans van Kranenburg <hans@xxxxxxxxxxx>
• Re: dm-integrity and bcache
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• dm-integrity and bcache
  • From: Robby Nelson <robertb.nelson@xxxxxxxxx>
• dm-integrity on bcache backing device
  • From: Robby Nelson <robertb.nelson@xxxxxxxxx>
• Re: Fwd: Linux (RHEL 7.6 with OSP 14) Bugs
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Fwd: Linux (RHEL 7.6 with OSP 14) Bugs
  • From: Amer Hwitat <amer.server.two@xxxxxxxxx>
• Re: Adiantum and integrity safe?
  • From: Kristian Klausen <kristian@xxxxxxxxxx>
• Re: Adiantum and integrity safe?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Share cryptsetup with luks for Android
  • From: Chandramohan <chandramohan.harkude@xxxxxxxxx>
• Re: Adiantum and integrity safe?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Adiantum and integrity safe?
  • From: Kristian Klausen <kristian@xxxxxxxxxx>
• Re: Luks header corruption
  • From: Jorge Fábregas <jorge.fabregas@xxxxxxxxx>
• Luks header corruption
  • From: Jivko Sabev <jivko.sabev@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.2.0-rc0 (experimental)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Is my LUKS header corrupted?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Is my LUKS header corrupted?
  • From: Greg Laun <cryptostuff744@xxxxxxxxx>
• Re: Is my LUKS header corrupted?
  • From: Heinz Diehl <htd+ml@xxxxxxxxxx>
• Re: Is my LUKS header corrupted?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Is my LUKS header corrupted?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Is my LUKS header corrupted?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Is my LUKS header corrupted?
  • From: Greg Laun <cryptostuff744@xxxxxxxxx>
• Re: Questions about FDE including /boot partition with detached USB
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Questions about FDE including /boot partition with detached USB (saout: to exclusive)
  • From: Diagon <saout.boxy@xxxxxxxx>
• Questions about FDE including /boot partition with detached USB
  • From: Selin Yukaribakmaz <selinyukaribakmaz@xxxxxxxxxxxxx>
• Re: Problem_wiping
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Problem_wiping
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Problem_wiping
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• unmount
  • From: Thorger Jansen <Service@xxxxxxxxxxxxxxxx>
• Problem_wiping
  • From: Dernsen <dernsen@xxxxxx>
• Re: Dm-crypt boot time passphrase visual feedback
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Dm-crypt boot time passphrase visual feedback
  • From: Mike Nagie <promike1987@xxxxxxxxx>
• Re: Dm-integrity freeze
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Dm-integrity freeze
  • From: Victor Helmholtz <victor.helmholtz@xxxxxxxxx>
• Re: Filesystem corruption with LVM's pvmove onto an encrypted volume with LUKS2 and a sector size of 4096
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Filesystem corruption with LVM's pvmove onto an encrypted volume with LUKS2 and a sector size of 4096
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: Filesystem corruption with LVM's pvmove onto an encrypted volume with LUKS2 and a sector size of 4096
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Filesystem corruption with LVM's pvmove onto an encrypted volume with LUKS2 and a sector size of 4096
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: Filesystem corruption with LVM's pvmove onto an encrypted volume with LUKS2 and a sector size of 4096
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Filesystem corruption with LVM's pvmove onto an encrypted volume with LUKS2 and a sector size of 4096
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Questions about LUKS mode of dm-crypt
  • From: "Mu Foto (Min)" <foto.mu@xxxxxxxxx>
• Re: How to get PBKDF settings of an existing key slot via libcryptsetup ?
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.1.0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: How to get PBKDF settings of an existing key slot via libcryptsetup ?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 'discard' as default
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: 'discard' as default
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: 'discard' as default
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: 'discard' as default
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: 'discard' as default
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Re: 'discard' as default
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: 'discard' as default
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• How to get PBKDF settings of an existing key slot via libcryptsetup ?
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: [PATCH] crypt_plain_hash: Remove dead code
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH] crypt_plain_hash: Remove dead code
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH] crypt_plain_hash: Remove dead code
  • From: Richard Weinberger <richard@xxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Question about "Add scsi_debug_teardown loop in blockwise tests."
  • From: yangerkun <yangerkun@xxxxxxxxxx>
• Re: Question about "Add scsi_debug_teardown loop in blockwise tests."
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: 'discard' as default
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Cryptsetup -- OpenSSL Engine
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Cryptsetup -- OpenSSL Engine
  • From: Anil Reddy <anilreddyy@xxxxxxxxx>
• Re: Cryptsetup -- OpenSSL Engine
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Cryptsetup -- OpenSSL Engine
  • From: Anil Reddy <anilreddyy@xxxxxxxxx>
• Re: 'discard' as default
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: 'discard' as default
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: 'discard' as default
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 'discard' as default
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: cryptsetup with kernel crypto backend and sha384
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 'discard' as default
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: 'discard' as default
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• 'discard' as default
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: 'discard' as default
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: 'discard' as default
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: 'discard' as default
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Question about "Add scsi_debug_teardown loop in blockwise tests."
  • From: yangerkun <yangerkun@xxxxxxxxxx>
• cryptsetup with kernel crypto backend and sha384
  • From: Simon Weissberg <Simon.Weissberg@xxxxxxxxxxxxxxxxx>
• 'discard' as default
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: question about usage of tcrypt-veracrypt and tcrypt-hidden
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• question about usage of tcrypt-veracrypt and tcrypt-hidden
  • From: cristiano prato <cristiano.prato@xxxxxxxxxxxxxxxxxxxxx>
• Re: LUKS2 and persistent keyrings to enable convenient EOL data destruction
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• LUKS2 and persistent keyrings to enable convenient EOL data destruction
  • From: "GMilos" <dm_crypt.1@xxxxxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.6
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup: WARNING: Target has an invalid header
  • From: Carabus Savvey <blsavvey@xxxxxxxxx>
• Re: cryptsetup: WARNING: Target has an invalid header
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: cryptsetup: WARNING: Target has an invalid header
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• cryptsetup: WARNING: Target has an invalid header
  • From: Carabus <blsavvey@xxxxxxxxx>
• Re: Data Processing Slowdown when LUKS used
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Data Processing Slowdown when LUKS used
  • From: H McCurdy <hmccurdy@xxxxxxxxx>
• Re: Unlocking LUKS2 with Sector Size > 512B
  • From: Martin Hicks <mort@xxxxxxxx>
• Re: Unlocking LUKS2 with Sector Size > 512B
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Unlocking LUKS2 with Sector Size > 512B
  • From: Martin Hicks <mort@xxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.5
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Stopped working.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Stopped working.
  • From: Γιώργος Κωστόπουλος <giorgosk67@xxxxxxxxx>
• Crypttab configuration questions.
  • From: Γιώργος Κωστόπουλος <giorgosk67@xxxxxxxxx>
• Re: Boot problem, after encrypting swap [SOLVED].
  • From: Γιώργος Κωστόπουλος <giorgosk67@xxxxxxxxx>
• Re: No prompt for decryption password every second or third boot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Boot problem, after encrypting swap.
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• No prompt for decryption password every second or third boot
  • From: Suresh Govindachar <sgovindachar@xxxxxxxxx>
• Re: Boot problem, after encrypting swap.
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Boot problem, after encrypting swap.
  • From: Γιώργος Κωστόπουλος <giorgosk67@xxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: cryptsetup --test-passphrase requires root
  • From: Frank Cusack <fr4nk@xxxxxxxx>
• Re: cryptsetup --test-passphrase requires root
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• cryptsetup --test-passphrase requires root
  • From: Frank Cusack <fr4nk@xxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Troubleshooting: Header Conversion to argon2id
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Troubleshooting: Header Conversion to argon2id
  • From: procmem <procmem@xxxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Argon2id security margin estimate and LUKS2 usage
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Argon2id security margin estimate and LUKS2 usage
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Argon2id security margin estimate and LUKS2 usage
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Argon2id security margin estimate and LUKS2 usage
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Argon2id security margin estimate and LUKS2 usage
  • From: procmem <procmem@xxxxxxxxxx>
• Re: Argon2id security margin estimate and LUKS2 usage
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Argon2id security margin estimate and LUKS2 usage
  • From: procmem <procmem@xxxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• some questions on dm-crypt/cryptsetup and LUKS2+integrity
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: AWS I3 Instance ephermal Volume Encryption
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• AWS I3 Instance ephermal Volume Encryption
  • From: rajpal reddy <rajpalreddy444@xxxxxxxxx>
• Re: Test suite is now FS-dependent
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Test suite is now FS-dependent
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: luksDump with --master-key-file fails to create nonexisting file
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• systemd & plymouth confusion when booting with multiple LUKS disks.
  • From: Diagon <saout.boxy@xxxxxxxx>
• luksDump with --master-key-file fails to create nonexisting file
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: Recreation of LUKS header when the master key is known
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: Test suite is now FS-dependent (Re: cryptsetup 2.0.4)
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Recreation of LUKS header when the master key is known
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Recreation of LUKS header when the master key is known
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Recreation of LUKS header when the master key is known
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Recreation of LUKS header when the master key is known
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Recreation of LUKS header when the master key is known
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: Test suite is now FS-dependent (Re: cryptsetup 2.0.4)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Test suite is now FS-dependent (Re: cryptsetup 2.0.4)
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.4
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: Debian installer formatting LUKS2 devices by default?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Debian installer formatting LUKS2 devices by default?
  • From: Guilhem Moulin <guilhem@xxxxxxxxxxx>
• Re: cryptsetup : LUKS2 Issue for using cryptsetup --type with aes-gcm-random
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• cryptsetup : LUKS2 Issue for using cryptsetup --type with aes-gcm-random
  • From: laurent cop <laurent.cop@xxxxxxxxx>
• Re: can't open LUKS drive after upgrade
  • From: brad <bradhaack@xxxxxxxxxxx>
• Re: can't open LUKS drive after upgrade
  • From: brad <bradhaack@xxxxxxxxxxx>
• Re: can't open LUKS drive after upgrade
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: can't open LUKS drive after upgrade
  • From: brad <bradhaack@xxxxxxxxxxx>
• Re: can't open LUKS drive after upgrade
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: can't open LUKS drive after upgrade
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: can't open LUKS drive after upgrade
  • From: brad <bradhaack@xxxxxxxxxxx>
• Re: can't open LUKS drive after upgrade
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup : LUKS2 Issue for using cryptsetup --type with aes-gcm-random
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• can't open LUKS drive after upgrade
  • From: brad <bradhaack@xxxxxxxxxxx>
• cryptsetup : LUKS2 Issue for using cryptsetup --type with aes-gcm-random
  • From: laurent cop <laurent.cop@xxxxxxxxx>
• Re: LUKS2 format documentation
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: dm-integrity standalone - lack of metadata
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-integrity standalone - lack of metadata
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Authenticated encryption in LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• LUKS2 format documentation
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup: lvm is not available
  • From: Stefan Klein <st.fankl.in@xxxxxxxxx>
• Re: [EXTERNAL] Re: DM-Verity + DM-Crypt error
  • From: "Nabar, Vidyesh" <Vidyesh.Nabar@xxxxxxxxxx>
• cryptsetup: lvm is not available
  • From: "ms ~" <ms3811@xxxxxxxxx>
• Re: dm-integrity standalone - lack of metadata
  • From: Harald Braumann <harry@xxxxxxxxxx>
• Re: dm-integrity standalone - lack of metadata
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-integrity standalone - lack of metadata
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• dm-integrity standalone - lack of metadata
  • From: Harald Braumann <harry@xxxxxxxxxx>
• Re: [EXTERNAL] Re: DM-Verity + DM-Crypt error
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Integrating luksSuspend in suspend to memory
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Re: Integrating luksSuspend in suspend to memory
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Integrating luksSuspend in suspend to memory
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: [EXTERNAL] Re: DM-Verity + DM-Crypt error
  • From: "Nabar, Vidyesh" <Vidyesh.Nabar@xxxxxxxxxx>
• Re: DM-Verity + DM-Crypt error
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• DM-Verity + DM-Crypt error
  • From: "Nabar, Vidyesh" <Vidyesh.Nabar@xxxxxxxxxx>
• LUKS 1.X - Wiping header vs wiping keyslots
  • From: qwrd <mistave@xxxxxxxxxxxxxxx>
• Re: Can't open luks after switching distros
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Can't open luks after switching distros
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Can't open luks after switching distros
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Can't open luks after switching distros
  • From: David Niklas <doark@xxxxxxxx>
• Re: Mildly OT: LUKS and the Debian installer
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: Mildly OT: LUKS and the Debian installer
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: sane distro-installer options for cryptsetup was: Mildly OT: LUKS and the Debian installer
  • From: Michael Ranft <m@xxxxxxxxxxxxxxxx>
• Re: sane distro-installer options for cryptsetup was: Mildly OT: LUKS and the Debian installer
  • From: Michael Ranft <m@xxxxxxxxxxxxxxxx>
• Re: Mildly OT: LUKS and the Debian installer
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: Mildly OT: LUKS and the Debian installer
  • From: Michael Ranft <m@xxxxxxxxxxxxxxxx>
• Re: Mildly OT: LUKS and the Debian installer
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: Mildly OT: LUKS and the Debian installer
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: Mildly OT: LUKS and the Debian installer
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Mildly OT: LUKS and the Debian installer
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Mildly OT: LUKS and the Debian installer
  • From: Diagon <saout.boxy@xxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.3
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Restricting rights of a particular slot of the 8 slots of passphrases for LUKS
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Restricting rights of a particular slot of the 8 slots of passphrases for LUKS
  • From: Suresh Govindachar <sgovindachar@xxxxxxxxx>
• Re: luks container write-protected and read-only, can't be mounted
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• luks container write-protected and read-only, can't be mounted
  • From: cici-tor <cici-tor@xxxxxxxxxxxxxx>
• Re: mdadm, luks, lvm, vm & trim
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: mdadm, luks, lvm, vm & trim
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: mdadm, luks, lvm, vm & trim
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: mdadm, luks, lvm, vm & trim
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: mdadm, luks, lvm, vm & trim
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: mdadm, luks, lvm, vm & trim
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• mdadm, luks, lvm, vm & trim
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: Extending to LUKS LVM, Ubuntu's instructions for recovering from a failed update: question on the nature of the USB
  • From: Suresh Govindachar <sgovindachar@xxxxxxxxx>
• Re: Does luksRemoveKey securely erase old keys?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Does luksRemoveKey securely erase old keys?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Does luksRemoveKey securely erase old keys?
  • From: tripleedgedsword <tripleedgedsword@xxxxxxxxxxxxxx>
• Extending to LUKS LVM, Ubuntu's instructions for recovering from a failed update
  • From: Suresh Govindachar <sgovindachar@xxxxxxxxx>
• device busy on scripted close
  • From: John Lane <dm-crypt@xxxxxxxxxxx>
• Re: mailing list working again
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• mailing list working again
  • From: Jana Saout <jana@xxxxxxxx>
• Re: Luks Key slot deletion question
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Luks Key slot deletion question
  • From: "Greenberg, Aria" <arcgreen@xxxxxx>
• GRUB and encrypted boot on usb, root on hdd. root is failing to mount/open
  • From: TM <boojum@xxxxxxxxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: configure: error: You need the uuid library.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• configure: error: You need the uuid library.
  • From: Rui Amaral <ruiam8@xxxxxxxxx>
• Re: dm-crypt overhead
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-crypt overhead
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: dm-crypt overhead
  • From: Lukáš Pohanka <numberfour@xxxxxxxxx>
• Re: dm-crypt overhead
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-crypt overhead
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: dm-crypt overhead
  • From: Lukáš Pohanka <numberfour@xxxxxxxxx>
• Re: dm-crypt overhead
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• dm-crypt overhead
  • From: Lukáš Pohanka <numberfour@xxxxxxxxx>
• Re: Mutithread Support
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Mutithread Support
  • From: Doug Meyer <dameyer@xxxxxxxxxxxx>
• Re: How to attach a LUKS header to an encrypted container?
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: How to attach a LUKS header to an encrypted container?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to attach a LUKS header to an encrypted container?
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: How to attach a LUKS header to an encrypted container?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: How to attach a LUKS header to an encrypted container?
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• How to attach a LUKS header to an encrypted container?
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: Are /dev objects required for clean shutdown?
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
• Re: Are /dev objects required for clean shutdown?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Are /dev objects required for clean shutdown?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Are /dev objects required for clean shutdown?
  • From: Pascal <Pascal@xxxxxxxx>
• Re: Open a LUKS container storing the operating system, with a header file in another location
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Open a LUKS container storing the operating system, with a header file in another location
  • From: 21naown@xxxxxxxxx
• Re: Open a LUKS container storing the operating system, with a header file in another location
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Open a LUKS container storing the operating system, with a header file in another location
  • From: 21naown@xxxxxxxxx
• Re: veritysetup verify successful but mount fails with new kernel
  • From: Mircea Gliga <mircea.gliga@xxxxxxxxxxx>
• Re: veritysetup verify successful but mount fails with new kernel
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• veritysetup verify successful but mount fails with new kernel
  • From: Mircea Gliga <mircea.gliga@xxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Correct rebuild process for hardware RAID 6 array with LUKS data ?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Correct rebuild process for hardware RAID 6 array with LUKS data ?
  • From: Hannes Erven <hannes@xxxxxxxx>
• Correct rebuild process for hardware RAID 6 array with LUKS data ?
  • From: nouser <wrangl3r@xxxxxxxx>
• Re: Several issues with cryptsetup 2.0.0
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
• Re: Questions about new ciphers
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Questions about new ciphers
  • From: Geo Kozey <geokozey@xxxxxxxxxxxxx>
• Re: Several issues with cryptsetup 2.0.0
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Several issues with cryptsetup 2.0.0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Fwd: [BUG] dm crypt: kernel keyring key processing bug
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Questions about new ciphers
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Several issues with cryptsetup 2.0.0
  • From: curve25519@xxxxxxxxxxx
• Re: Several issues with cryptsetup 2.0.0
  • From: curve25519@xxxxxxxxxxx
• Re: Several issues with cryptsetup 2.0.0
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Several issues with cryptsetup 2.0.0
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Several issues with cryptsetup 2.0.0
  • From: curve25519@xxxxxxxxxxx
• Questions about new ciphers
  • From: Geo Kozey <geokozey@xxxxxxxxxxxxx>
• Re: Creating dm-crypt target from the second sector?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Creating dm-crypt target from the second sector?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Creating dm-crypt target from the second sector?
  • From: Lukáš Pohanka <numberfour@xxxxxxxxx>
• Re: mistake with luksFormat
  • From: H McCurdy <hmccurdy@xxxxxxxxx>
• Re: mistake with luksFormat
  • From: Wensday <michalwenda1@xxxxxxxxx>
• Re: Two questions about LUKS2 format
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Two questions about LUKS2 format
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Two questions about LUKS2 format
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Two questions about LUKS2 format
  • From: Geo Kozey <geokozey@xxxxxxxxxxxxx>
• Re: broken link: Fru05b in pub/linux/utils/cryptsetup/LUKS_docs/on-disk-format.pdf
  • From: Slim2k <slim2k@xxxxxxxxxxxxxx>
• Re: cryptsetup on linear md
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: broken link: Fru05b in pub/linux/utils/cryptsetup/LUKS_docs/on-disk-format.pdf
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: broken link: Fru05b in pub/linux/utils/cryptsetup/LUKS_docs/on-disk-format.pdf
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: broken link: Fru05b in pub/linux/utils/cryptsetup/LUKS_docs/on-disk-format.pdf
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• broken link: Fru05b in pub/linux/utils/cryptsetup/LUKS_docs/on-disk-format.pdf
  • From: Slim2k <slim2k@xxxxxxxxxxxxxx>
• cryptsetup on linear md
  • From: Sverd Johnsen <sverd.johnsen@xxxxxxxxxxxxxx>
• Re: mistake with luksFormat
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: mistake with luksFormat
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: mistake with luksFormat
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: mistake with luksFormat
  • From: "A. Kapetanovic" <aka@xxxxxxxxxxx>
• Re: mistake with luksFormat
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• mistake with luksFormat
  • From: "A. Kapetanovic" <aka@xxxxxxxxxxx>
• Re: LUKS2 resizing
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: LUKS2 resizing
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: LUKS2 resizing
  • From: Andrius Štikonas <andrius@xxxxxxxxxxx>
• Re: LUKS2 resizing
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• LUKS2 resizing
  • From: Andrius Štikonas <andrius@xxxxxxxxxxx>
• A disk/device/guid in cryptomodule
  • From: "Ruslan R. Laishev" <zator@xxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.0.0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.0.0
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: FIPS validated
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: FIPS validated
  • From: H McCurdy <hmccurdy@xxxxxxxxx>
• FIPS validated
  • From: Jerry Lowry <jlowry@xxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.0.0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.0.0
  • From: Geo Kozey <geokozey@xxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: kernel: CONFIG_KEYS
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• kernel: CONFIG_KEYS
  • From: Karel <lists@xxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: protagonist <protagonist@xxxxxxxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Jindrich Kolman <kolman.jindrich@xxxxxxxxx>
• timeout issue
  • From: David B <davidmberten@xxxxxxxxx>
• Cryptsetup
  • From: Steven Houtchen <shoutchen@xxxxxxxxx>
• Re: Prepare SSD for encrypted linux install
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Prepare SSD for encrypted linux install
  • From: Merlin Büge <toni@xxxxxxxxxxxx>
• Re: Prepare SSD for encrypted linux install
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Prepare SSD for encrypted linux install
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Prepare SSD for encrypted linux install
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: Prepare SSD for encrypted linux install
  • From: Heinz Diehl <htd+ml@xxxxxxxxxx>
• Prepare SSD for encrypted linux install
  • From: Merlin Büge <toni@xxxxxxxxxxxx>
• Re: Can I test for LUKS passphrase strength without formatting a device?
  • From: Jan Tulak <jtulak@xxxxxxxxxx>
• Re: Can I test for LUKS passphrase strength without formatting a device?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Can I test for LUKS passphrase strength without formatting a device?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Can I test for LUKS passphrase strength without formatting a device?
  • From: Jan Tulak <jtulak@xxxxxxxxxx>
• Cryptsetup cross compiling for ARM fails
  • From: Moshe Kravchik <mkravchik@xxxxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.0.0-rc1
  • From: Geo Kozey <geokozey@xxxxxxxxxxxxx>
• Re: Help with cross compilation needed
  • From: Marco Cavallini <m.cavallini@xxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.0.0-rc1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Help with cross compilation needed
  • From: Moshe Kravchik <mkravchik@xxxxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.0.0-rc1
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.0.0-rc1
  • From: Geo Kozey <geokozey@xxxxxxxxxxxxx>
• Re: git version of zuluCrypt already supports LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.0-rc1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Disadvantages of many temporary keys?
  • From: Claudio Moretti <flyingstar16@xxxxxxxxx>
• Re: Disadvantages of many temporary keys?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Disadvantages of many temporary keys?
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Disadvantages of many temporary keys?
  • From: "L. Rose" <lists@xxxxxxxx>
• Re: Dm-Verity on UBI/UBIFS
  • From: Marco Cavallini <m.cavallini@xxxxxxxxxxxxxxxx>
• Re: Dm-Verity on UBI/UBIFS
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Dm-Verity on UBI/UBIFS
  • From: Marco Cavallini <m.cavallini@xxxxxxxxxxxxxxxx>
• Re: Veritysetup
  • From: Viacheslav Salnikov <slavasalnikovv@xxxxxxxxx>
• Re: Veritysetup
  • From: Viacheslav Salnikov <slavasalnikovv@xxxxxxxxx>
• Dm-Verity on UBI/UBIFS
  • From: "Islam, Akm Moinul" <AkmMoinul.Islam@xxxxxxxxxx>
• Re: Veritysetup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Veritysetup
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Veritysetup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Veritysetup
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Veritysetup
  • From: Viacheslav Salnikov <slavasalnikovv@xxxxxxxxx>
• Request concerning privacy innovation research (reminder)
  • From: Ben Hup <b.m.hup@xxxxxxxxxxxxxxxxxx>
• Re: cryptsetup --veracrypt opens legacy TrueCrypt volumes
  • From: segfault <segfault@xxxxxxxxxx>
• Re: cryptsetup --veracrypt opens legacy TrueCrypt volumes
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• cryptsetup --veracrypt opens legacy TrueCrypt volumes
  • From: segfault <segfault@xxxxxxxxxx>
• git version of zuluCrypt already supports LUKS2
  • From: ".. ink .." <mhogomchungu@xxxxxxxxx>
• Re: problems mounting encrypted drive on reboot
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.0.0-rc0 (TESTING version with experimental features)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Latency penalty
  • From: Ivan Babrou <ibobrik@xxxxxxxxx>
• Re: Latency penalty
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Latency penalty
  • From: Ivan Babrou <ibobrik@xxxxxxxxx>
• Re: problems mounting encrypted drive on reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: problems mounting encrypted drive on reboot
  • From: Jerry Lowry <jlowry@xxxxxxx>
• Re: problems mounting encrypted drive on reboot
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: problems mounting encrypted drive on reboot
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: problems mounting encrypted drive on reboot
  • From: Jerry Lowry <jlowry@xxxxxxx>
• Re: problems mounting encrypted drive on reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• problems mounting encrypted drive on reboot
  • From: Jerry Lowry <jlowry@xxxxxxx>
• Re: Help What is ./configure --with-crypto_backend=openssl for?
  • From: Tung Nguyen <tungn@xxxxxxxxxxxx>
• Re: Add --iter-count in order to not use --iter-time
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Help What is ./configure --with-crypto_backend=openssl for?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Help What is ./configure --with-crypto_backend=openssl for?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Help What is ./configure --with-crypto_backend=openssl for?
  • From: Tung Nguyen <tungn@xxxxxxxxxxxx>
• Re: Add --iter-count in order to not use --iter-time
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Add --iter-count in order to not use --iter-time
  • From: Oliver Smith <ollieparanoid@xxxxxxxxxxxxx>
• Re: luksSuspend for plain dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: luksSuspend for plain dm-crypt
  • From: dm-crypt@xxxxxxxxxxxxxxxxx
• Re: luksSuspend for plain dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• luksSuspend for plain dm-crypt
  • From: dm-crypt@xxxxxxxxxxxxxxxxx
• Re: Decrypt a volume without user intervention
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Decrypt a volume without user intervention
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
• Re: Decrypt a volume without user intervention
  • From: Marco Cavallini <cavallini.koan@xxxxxxxxx>
• Re: Decrypt a volume without user intervention
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Decrypt a volume without user intervention
  • From: Marco Cavallini <cavallini.koan@xxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: angelomariafederichini191269 <angelomariafederichini191269@xxxxxxxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: Richard Z <rz@xxxxxxxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: angelomariafederichini191269 <angelomariafederichini191269@xxxxxxxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: [PATCH] Speed up keyfile reading
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH] Speed up keyfile reading
  • From: angelomariafederichini191269 <angelomariafederichini191269@xxxxxxxxxxxxxx>
• Re: Request for Comments about Chained-IV feature in Linux crypto framework
  • From: "Yu, Wenqian" <wenqian.yu@xxxxxxxxx>
• Re: cryptsetup-reencrypt additional options
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup-reencrypt additional options
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• cryptsetup-reencrypt additional options
  • From: Perry Thompson <contact@xxxxxxxxx>
• Fwd: Re: Computer locking up on heavy disk IO
  • From: heinrich5991@xxxxxxxxx
• Re: Computer locking up on heavy disk IO
  • From: heinrich5991@xxxxxxxxx
• Re: Computer locking up on heavy disk IO
  • From: heinrich5991@xxxxxxxxx
• Re: Computer locking up on heavy disk IO
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Computer locking up on heavy disk IO
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Computer locking up on heavy disk IO
  • From: heinrich5991@xxxxxxxxx
• Re: Computer locking up on heavy disk IO
  • From: heinrich5991@xxxxxxxxx
• Re: Computer locking up on heavy disk IO
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Computer locking up on heavy disk IO
  • From: heinrich5991@xxxxxxxxx
• Re: I never setup a sda5 crypt
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• I never setup a sda5 crypt
  • From: jamsjams2 <jamsjams2playz@xxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Reading the serial number of an HDD encrypted with dm-crypt
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Reading the serial number of an HDD encrypted with dm-crypt
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Reading the serial number of an HDD encrypted with dm-crypt
  • From: Rehan Iftikhar <rehan.iftikhar@xxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Julio Gago <julio.gago@xxxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Julio Gago <julio.gago@xxxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Julio Gago <julio.gago@xxxxxxxxxxxx>
• Re: help mounting partitions in an encrypted disk after first reboot
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• help mounting partitions in an encrypted disk after first reboot
  • From: Julio Gago <julio.gago@xxxxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
• Re: [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Hendrik Brueckner <brueckner@xxxxxxxxxxxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Hendrik Brueckner <brueckner@xxxxxxxxxxxxxxxxxx>
• Re: Git update > make fails
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Git update > make fails
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Git update > make fails
  • From: Demian Smith <demian.smith@xxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: David Niklas <doark@xxxxxxxx>
• Re: Shipping/Cloning encrypted disks
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Shipping/Cloning encrypted disks
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Shipping/Cloning encrypted disks
  • From: <vasili@xxxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Hendrik Brueckner <brueckner@xxxxxxxxxxxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Hendrik Brueckner <brueckner@xxxxxxxxxxxxxxxxxx>
• Re: (no subject)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: (no subject)
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: (no subject)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: (no subject)
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: (no subject)
  • From: Hammad Siddiqi <hsiddiqi@xxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: protagonist <listdump@xxxxxxxxxxxxxxxxxxxx>
• Re: (no subject)
  • From: Hammad Siddiqi <hsiddiqi@xxxxxxxxx>
• No key available with this passphrase
  • From: Hammad Siddiqi <hsiddiqi@xxxxxxxxx>
• Re: (no subject)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• (no subject)
  • From: Hammad Siddiqi <hsiddiqi@xxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: protagonist <listdump@xxxxxxxxxxxxxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Managing wrapped key ciphers with cryptsetup
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
• Managing wrapped key ciphers with cryptsetup
  • From: Hendrik Brueckner <brueckner@xxxxxxxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 1.7.5
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Hendrik Brueckner <brueckner@xxxxxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: protagonist <listdump@xxxxxxxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: protagonist <listdump@xxxxxxxxxxxxxxxxxxxx>
• Re: Fwd: Regarding Cryptsetup
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Fwd: Regarding Cryptsetup
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Fwd: Regarding Cryptsetup
  • From: Karthikeyan Ramsamy <karthik.3.cit@xxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
  • From: protagonist <listdump@xxxxxxxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt, bruteforce detection of bit errors
  • From: protagonist <listdump@xxxxxxxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt from apparently healthy SSD
  • From: Arno Wagner <arno@xxxxxxxxxxx>