Device-Mapper Crypto

• Thread Index

• Re: LUKS header recovery attempt from apparently healthy SSD
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Fwd: Detect successful passphrase entry for dmcrypt +LUKS from initramfs busybox prompt
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Fwd: Detect successful passphrase entry for dmcrypt +LUKS from initramfs busybox prompt
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: Fwd: Detect successful passphrase entry for dmcrypt +LUKS from initramfs busybox prompt
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Fwd: Detect successful passphrase entry for dmcrypt +LUKS from initramfs busybox prompt
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: LUKS header recovery attempt from apparently healthy SSD
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS header recovery attempt from apparently healthy SSD
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: Detect successful passphrase entry for dmcrypt +LUKS from initramfs busybox prompt
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• LUKS header recovery attempt from apparently healthy SSD
  • From: protagonist <listdump@xxxxxxxxxxxxxxxxxxxx>
• Detect successful passphrase entry for dmcrypt +LUKS from initramfs busybox prompt
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Failure to encrypt a big disk - missing kernel module?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Failure to encrypt a big disk - missing kernel module?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Detached header offset
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Detached header offset
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Detached header offset
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Detached header offset
  • From: 7heo <7heo@xxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: 7heo <7heo@xxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: 7heo <7heo@xxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: 7heo <7heo@xxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: 7heo <7heo@xxxxxxxx>
• Re: Detached headers, multiple drives and UUIDs
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Detached headers, multiple drives and UUIDs
  • From: 7heo <7heo@xxxxxxxx>
• Re: NIST random number generators
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: NIST random number generators
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• NIST random number generators
  • From: "Houtchen, Steven" <shoutchen@xxxxxxxxxxxxxxxxx>
• Re: Best practice for storing header backup and protecting against mistakes/misuse.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Best practice for storing header backup and protecting against mistakes/misuse.
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Best practice for storing header backup and protecting against mistakes/misuse.
  • From: Waqar Khan <waqark3389temp@xxxxxxxxx>
• Re: Best practice for storing header backup and protecting against mistakes/misuse.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Best practice for storing header backup and protecting against mistakes/misuse.
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Best practice for storing header backup and protecting against mistakes/misuse.
  • From: Waqar Khan <waqark3389temp@xxxxxxxxx>
• Re: Unable to dump header with --dump-master-key
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Unable to dump header with --dump-master-key
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Unable to dump header with --dump-master-key
  • From: Waqar Khan <waqark3389temp@xxxxxxxxx>
• Unable to dump header with --dump-master-key
  • From: Waqar Khan <waqark3389temp@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 1.7.4
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Cryptsetup-reencrypt and data integrity.
  • From: "daniel@xxxxxxxxxxx" <daniel@xxxxxxxxxxx>
• Re: Cryptsetup-reencrypt and data integrity.
  • From: "daniel@xxxxxxxxxxx" <daniel@xxxxxxxxxxx>
• Re: Cryptsetup-reencrypt and data integrity.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Cryptsetup-reencrypt and data integrity.
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Cryptsetup-reencrypt and data integrity.
  • From: "daniel@xxxxxxxxxxx" <daniel@xxxxxxxxxxx>
• Re: General question: Encrypytion on virtual servers (VPS/Vserver)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: General question: Encrypytion on virtual servers (VPS/Vserver)
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: General question: Encrypytion on virtual servers (VPS/Vserver)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: General question: Encrypytion on virtual servers (VPS/Vserver)
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: General question: Encrypytion on virtual servers (VPS/Vserver)
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: General question: Encrypytion on virtual servers (VPS/Vserver)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• General question: Encrypytion on virtual servers (VPS/Vserver)
  • From: "michaelof@xxxxxxxxxxxxxx" <michaelof@xxxxxxxxxxxxxx>
• Re: Question about how data is read using dm-crypt
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Question about how data is read using dm-crypt
  • From: 박마루한 <mrpark@xxxxxxxxxxxxxxxxx>
• Re: cryptsetup manpage: misleading/imprecise description of --size for resize
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• cryptsetup manpage: misleading/imprecise description of --size for resize
  • From: "G.raud" <graud@xxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: "Houtchen, Steven" <shoutchen@xxxxxxxxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: crypetsetup and GPT partitions
  • From: "Houtchen, Steven" <shoutchen@xxxxxxxxxxxxxxxxx>
• crypetsetup and GPT partitions
  • From: "Houtchen, Steven" <shoutchen@xxxxxxxxxxxxxxxxx>
• Re: found more than one resume device candidate
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: found more than one resume device candidate
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• found more than one resume device candidate
  • From: scar <scar@xxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: K Mmmm <1800ponysauce@xxxxxxxxx>
• Re: cryptsetup FAQ section 6.10, master keys and cryptsetup-reencrypt (resend)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• cryptsetup FAQ section 6.10, master keys and cryptsetup-reencrypt (resend)
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Laurence Darby <ldarby@xxxxxxxxxxxx>
• cryptsetup FAQ section 6.10, master keys and cryptsetup-reencrypt
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Decrypting a drive; says a correct password is "incorrect"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: GEOM_ELI support in dm-crypt/cryptsetup
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: GEOM_ELI support in dm-crypt/cryptsetup
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Decrypting a drive; says a correct password is "incorrect"
  • From: K Mmmm <1800ponysauce@xxxxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Laurence Darby <ldarby@xxxxxxxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Sophie Hunt <sophie.hunt@xxxxxxxxxxxxxx>
• Re: Cryptsetup FAQ monthly posting 1/2017
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Cryptsetup FAQ monthly posting 1/2017
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: GEOM_ELI support in dm-crypt/cryptsetup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Cryptsetup FAQ monthly posting 1/2017
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Cryptsetup FAQ monthly posting 1/2017
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Cryptsetup FAQ monthly posting 1/2017
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Cryptsetup bug
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: GEOM_ELI support in dm-crypt/cryptsetup
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: Cryptsetup bug
  • From: Hunter DeMeyer <hd4pix@xxxxxxxxx>
• Re: Cryptsetup bug
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Cryptsetup bug
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Cryptsetup bug
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Cryptsetup bug
  • From: Hunter DeMeyer <hd4pix@xxxxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: GEOM_ELI support in dm-crypt/cryptsetup
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: GEOM_ELI support in dm-crypt/cryptsetup
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: TrueCrypt is discontinued - here are the alternatives
  • From: Sophie Hunt <sophie.hunt@xxxxxxxxxxxxxx>
• Re: Determining which slot was used to unlock a LUKS device
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Determining which slot was used to unlock a LUKS device
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Determining which slot was used to unlock a LUKS device
  • From: Kamran Khan <krkhan@xxxxxxxxxxxxxx>
• Re: Restore LUKS partition
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Restore LUKS partition
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Restore LUKS partition
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Restore LUKS partition
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Restore LUKS partition
  • From: Oskar Jauch <oskar.jauch@xxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Typo in the cryptsetup FAQ
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Typo in the cryptsetup FAQ
  • From: "Chloris ." <chloris@xxxxxxxxxx>
• Re: sha384, sha512
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• sha384, sha512
  • From: "Houtchen, Steven" <shoutchen@xxxxxxxxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: David Niklas <doark@xxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• About CVE-2016-4484: - Cryptsetup Initrd root Shell
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: License Clarification
  • From: Nathaniel McCallum <npmccallum@xxxxxxxxxx>
• Re: License Clarification
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• License Clarification
  • From: Nathaniel McCallum <npmccallum@xxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope? SOLVED
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: zero.tonin@xxxxxx
• Re: Missing keyslot or broken header or still some hope?
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: zero.tonin@xxxxxx
• Re: Missing keyslot or broken header or still some hope?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: Heinz Diehl <htd+ml@xxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: zero.tonin@xxxxxx
• Re: Missing keyslot or broken header or still some hope?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: zero.tonin@xxxxxx
• Re: Missing keyslot or broken header or still some hope?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: Zero Tonin <zero.tonin@xxxxxx>
• Re: Missing keyslot or broken header or still some hope?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Missing keyslot or broken header or still some hope?
  • From: Zero Tonin <zero.tonin@xxxxxx>
• Re: misprint in "cryptsetup.c"
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• misprint in "cryptsetup.c"
  • From: "Alexey Pronyaev" <alexey.pronyaev@xxxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 1.7.3
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: pashphrase management question
  • From: "ClEmFoster" <clemfoster@xxxxxxxxxxxxx>
• Re: pashphrase management question
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: pashphrase management question
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: pashphrase management question
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: pashphrase management question
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: pashphrase management question
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: pashphrase management question
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: pashphrase management question
  • From: "ClEmFoster" <clemfoster@xxxxxxxxxxxxx>
• Re: pashphrase management question
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: pashphrase management question
  • From: "ClEmFoster" <clemfoster@xxxxxxxxxxxxx>
• Re: pashphrase management question
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• pashphrase management question
  • From: "ClEmFoster" <clemfoster@xxxxxxxxxxxxx>
• Re: How to suspend to disk with random encrypted swap
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: How to suspend to disk with random encrypted swap
  • From: Heiko Rosemann <heiko.rosemann@xxxxxx>
• Re: How to suspend to disk with random encrypted swap
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• How to suspend to disk with random encrypted swap
  • From: David Niklas <doark@xxxxxxxx>
• Re: LUKS related question
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: LUKS related question
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• LUKS related question
  • From: Nikolai Nedovodin <info@xxxxxxxxxx>
• Re: Broken link to LUKS format specifications
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Broken link to LUKS format specifications
  • From: Francesco Merati <francesmera@xxxxxxxxx>
• Re: Memory leak when using openssl backend
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Memory leak when using openssl backend
  • From: Per Johansson <per.x.johansson@xxxxxxxx>
• Re: Using a keyfile with full disk encryption (saout: to exclusive)
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: Using a keyfile with full disk encryption
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Using a keyfile with full disk encryption
  • From: Tim Kerby <me@xxxxxxxxx>
• Using a keyfile with full disk encryption
  • From: Tim Kerby <tkerby@xxxxxxxxxxxxxx>
• Re: How to record "secrets" and get them back with pgp ?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to record "secrets" and get them back with pgp ?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to record "secrets" and get them back with pgp ?
  • From: "Arbiel (gmx)" <arbiel.perlacremaz@xxxxxx>
• Re: How to record "secrets" and get them back with pgp ?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: How to record "secrets" and get them back with pgp ?
  • From: "Arbiel (gmx)" <arbiel.perlacremaz@xxxxxx>
• Re: Hang problem with dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: How to record "secrets" and get them back with pgp ?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• How to record "secrets" and get them back with pgp ?
  • From: "Arbiel (gmx)" <arbiel.perlacremaz@xxxxxx>
• Re: Hang problem with dm-crypt
  • From: "Yu, Wenqian" <wenqian.yu@xxxxxxxxx>
• Re: Hang problem with dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Hang problem with dm-crypt
  • From: "Yu, Wenqian" <wenqian.yu@xxxxxxxxx>
• Re: Questions on LUKS
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Questions on LUKS
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Questions on LUKS
  • From: "Ruiz, Edwin" <eruiz03@xxxxxxxxxx>
• Re: [PATCH v1] luks1: fix pbkdf iteration estimation with sha1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH v1] luks1: fix pbkdf iteration estimation with sha1
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: [PATCH v1] luks1: fix pbkdf iteration estimation with sha1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH v1] luks1: fix pbkdf iteration estimation with sha1
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: Upgrading to latest version
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Upgrading to latest version
  • From: Marco Silva <marcosilva0000@xxxxxxxxx>
• Re: cryptsetup-reencrypt --new should ask for new password twice
  • From: David Niklas <doark@xxxxxxxx>
• Re: cryptsetup-reencrypt --new should ask for new password twice
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• cryptsetup-reencrypt --new should ask for new password twice
  • From: Urs Schulz <dmcrypt@xxxxxxxxxxxx>
• Re: What does the "create" action do?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• What does the "create" action do?
  • From: 박마루한 <mrpark@xxxxxxxxxxxxxxxxx>
• Re: How to determine if a LUKS device is opened or closed
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to determine if a LUKS device is opened or closed
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• How to determine if a LUKS device is opened or closed
  • From: Tom Hartman <rokstar83@xxxxxxxxx>
• Re: LUKS encrypted hard disk crashed. Recovery question
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS encrypted hard disk crashed. Recovery question
  • From: Saibal Kumar Adhya <saibalka@xxxxxxxxxxx>
• Re: LUKS encrypted hard disk crashed. Recovery question
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• LUKS encrypted hard disk crashed. Recovery question
  • From: Saibal Kumar Adhya <saibalka@xxxxxxxxxxx>
• Re: [No key available with this passphrase.]
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: [No key available with this passphrase.]
  • From: Valentin Buza <valentinbuza92@xxxxxxxxx>
• Re: [No key available with this passphrase.]
  • From: Valentin Buza <valentinbuza92@xxxxxxxxx>
• Re: [No key available with this passphrase.]
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: [No key available with this passphrase.]
  • From: Valentin Buza <valentinbuza92@xxxxxxxxx>
• Re: [No key available with this passphrase.]
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• [No key available with this passphrase.]
  • From: Cristian-Valentin BUZ? <cristian.buza@xxxxxxxxxx>
• Re: some explanations would be welcome
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: some explanations would be welcome
  • From: Lars Winterfeld <lars.winterfeld@xxxxxxxxxxxxx>
• some explanations would be welcome
  • From: Pascal <patatetom@xxxxxxxxx>
• Re: Issue with crypttab
  • From: "Arbiel (gmx)" <arbiel.perlacremaz@xxxxxx>
• Re: Issue with crypttab
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Issue with crypttab
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Issue with crypttab
  • From: "Arbiel (gmx)" <arbiel.perlacremaz@xxxxxx>
• Re: Issue with crypttab
  • From: "Arbiel (gmx)" <arbiel.perlacremaz@xxxxxx>
• Re: Issue with crypttab
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Issue with crypttab
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Issue with crypttab
  • From: "Jacques Berger" <jacques.berger@xxxxxx>
• Re: Offset/size issue during LUKS recovery.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Offset/size issue during LUKS recovery.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Offset/size issue during LUKS recovery.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to mount a dm-verity volume?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Offset/size issue during LUKS recovery.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Offset/size issue during LUKS recovery.
  • From: "Julio Cesar Faracco" <jfaracco@xxxxxxxxxx>
• How to mount a dm-verity volume?
  • From: Gyula Kovács <gyula.kovacs.kkb.tech@xxxxxxxxx>
• Re: Please do not ignore.. this is so important to me.. Lost password
  • From: H McCurdy <hmccurdy@xxxxxxxxx>
• Re: Please do not ignore.. this is so important to me.. Lost password
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Please do not ignore.. this is so important to me.. Lost password
  • From: kranthi <kranthi.doss@xxxxxxxxx>
• Re: luksAddKey hangs for ~85 minutes and then fails
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: dm-crypt.ko external kernel module
  • From: Tapas Sarangi <TSarangi@xxxxxxxxxxxxx>
• Re: dm-crypt.ko external kernel module
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• dm-crypt.ko external kernel module
  • From: Tapas Sarangi <TSarangi@xxxxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Bernd Brägelmann <bernd@xxxxxxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Bernd Brägelmann <bernd@xxxxxxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Bernd Brägelmann <bernd@xxxxxxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Incidentaly partitioned LUKS device - header lost?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Incidentaly partitioned LUKS device - header lost?
  • From: Bernd Brägelmann <bernd@xxxxxxxxxxxxxxx>
• Cryptsetup FAQ montly posting 7/2016
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Police Terror <PoliceTerror@xxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Police Terror <PoliceTerror@xxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: luksFormat still spinning/hanging with large array on kernel 4.6.2
  • From: Charles Cazabon <charlesc@xxxxxxxxxx>
• Re: unlock luks volume using valid keyslot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: unlock luks volume using valid keyslot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: unlock luks volume using valid keyslot
  • From: Oko Hid <randomwalker0201@xxxxxxxxx>
• Re: unlock luks volume using valid keyslot
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• unlock luks volume using valid keyslot
  • From: Oko Hid <randomwalker0201@xxxxxxxxx>
• Re: Does luksFormat write the full size of the device?
  • From: Charles Cazabon <charlesc@xxxxxxxxxx>
• Re: luksFormat still spinning/hanging with large array on kernel 4.6.2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: luksFormat still spinning/hanging with large array on kernel 4.6.2
  • From: Charles Cazabon <charlesc@xxxxxxxxxx>
• [charlesc@xxxxxxxxxx: Re: Does luksFormat write the full size of the device?]
  • From: Charles Cazabon <charlesc@xxxxxxxxxx>
• Re: Does luksFormat write the full size of the device?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Does luksFormat write the full size of the device?
  • From: Charles Cazabon <charlesc@xxxxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Police Terror <PoliceTerror@xxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Police Terror <PoliceTerror@xxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes (saout: to exclusive)
  • From: Police Terror <PoliceTerror@xxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Police Terror <PoliceTerror@xxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes (saout: to exclusive)
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: cryptsetup with Python subprocess + pipes
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• cryptsetup with Python subprocess + pipes
  • From: Police Terror <PoliceTerror@xxxxxxxx>
• Re: luksAddKey hangs for ~85 minutes and then fails
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: luksAddKey hangs for ~85 minutes and then fails
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: luksAddKey hangs for ~85 minutes and then fails
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: luksAddKey hangs for ~85 minutes and then fails
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: luksAddKey hangs for ~85 minutes and then fails
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• luksAddKey hangs for ~85 minutes and then fails
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: (no subject)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: (no subject)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• (no subject)
  • From: RAS RAS <ras-os@xxxxxxx>
• Re: Block size and tweak value
  • From: jonetsu <jonetsu@xxxxxxxxxxxx>
• Re: Block size and tweak value
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Block size and tweak value
  • From: jonetsu <jonetsu@xxxxxxxxxxxx>
• Re: hi.. Suggestions and questions.
  • From: Lars Winterfeld <lars.winterfeld@xxxxxxxxxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: fauno <fauno@xxxxxxxxxxxxxxxxxxxx>
• hi.. Suggestions and questions.
  • From: 동우 <candan@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 1.7.2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: security concerns with RAID on top of dmcrpyt and with mulitple devices with the same key slot key?
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: security concerns with RAID on top of dmcrpyt and with mulitple devices with the same key slot key?
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: security concerns with RAID on top of dmcrpyt and with mulitple devices with the same key slot key?
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• security concerns with RAID on top of dmcrpyt and with mulitple devices with the same key slot key?
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: fauno <fauno@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] dm-log-writes: fix bug with too large bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-log-writes: fix bug with too large bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-log-writes: fix bug with too large bios
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• Re: [PATCH] dm-crypt: Fix error with too large bios (was: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size)
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• Re: dm-crypt LUKS and USB power management
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: fauno <fauno@xxxxxxxxxxxxxxxxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: dm-crypt LUKS and USB power management
  • From: Axel Heider <axelheider@xxxxxx>
• Re: LVM on LUKS: volumes missing
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: dm-crypt LUKS and USB power management
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxxxxxx>
• LVM on LUKS: volumes missing
  • From: fauno <fauno@xxxxxxxxxxxxxxxxxxxx>
• LVM on LUKS: volumes missing
  • From: fauno <fauno@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] dm-log-writes: fix bug with too large bios
  • From: Josef Bacik <jbacik@xxxxxx>
• [PATCH] dm-crypt: Fix error with too large bios (was: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size)
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-log-writes: fix bug with too large bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
  • From: Aaron <lists@xxxxxxxxxxxxxxxxxx>
• [BISECT dbba42d8] dm: regression: large bio splits fail with dm-crypt under bcache in dm_make_request()
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: Initializing dm-crypt on Android results in "device lookup failed"
  • From: Roman Schlegel <lists@xxxxxxx>
• Re: Initializing dm-crypt on Android results in "device lookup failed"
  • From: Roman Schlegel <lists@xxxxxxx>
• Re: Initializing dm-crypt on Android results in "device lookup failed"
  • From: Roman Schlegel <lists@xxxxxxx>
• Re: A couple of strings that could be reviewed
  • From: Rafael Fontenelle <rffontenelle@xxxxxxxxx>
• dm-verity error s6 edge G925F
  • From: Luka Jovanic <jovanickg@xxxxxxxxx>
• Re: Initializing dm-crypt on Android results in "device lookup failed"
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: A couple of strings that could be reviewed
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Initializing dm-crypt on Android results in "device lookup failed"
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Initializing dm-crypt on Android results in "device lookup failed"
  • From: Roman Schlegel <lists@xxxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• Re: /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
  • From: Hugh Bragg <hughbragg@xxxxxxxxxxx>
• Re: /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
  • From: Aaron <lists@xxxxxxxxxxxxxxxxxx>
• Re: A couple of strings that could be reviewed
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• A couple of strings that could be reviewed
  • From: Rafael Fontenelle <rffontenelle@xxxxxxxxx>
• dm-crypt LUKS and USB power management
  • From: Axel Heider <axelheider@xxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: "'Eric Wheeler'" <bcache@xxxxxxxxxxxxxxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: [dm-devel] bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: PKCS#11 support in cryptsetup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [ANNOUNCE] LUKSMeta
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [ANNOUNCE] LUKSMeta
  • From: Nathaniel McCallum <npmccallum@xxxxxxxxxx>
• Re: [ANNOUNCE] LUKSMeta
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• [ANNOUNCE] LUKSMeta
  • From: Nathaniel McCallum <npmccallum@xxxxxxxxxx>
• Re: bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• bcache gets stuck flushing writeback cache when used in combination with LUKS/dm-crypt and non-default bucket size
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• Re: PKCS#11 support in cryptsetup
  • From: Johanna A <johanna-a@xxxxxxxx>
• Re: PKCS#11 support in cryptsetup
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• PKCS#11 support in cryptsetup
  • From: Johanna A <johanna-a@xxxxxxxx>
• Re: Cryptesetup and dm-crypt
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Cryptesetup and dm-crypt
  • From: levent demir <levent.demir@xxxxxxxx>
• Re: LUKS partition write-protected, mounting read-only
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: LUKS partition write-protected, mounting read-only
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• LUKS partition write-protected, mounting read-only
  • From: Serrano Pereira <serrano.pereira@xxxxxxxxx>
• Re: unknown version
  • From: Julien Lepiller <julien@xxxxxxxxxxx>
• Re: unknown version
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: unknown version
  • From: Julien Lepiller <julien@xxxxxxxxxxx>
• Re: unknown version
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• unknown version
  • From: Julien Lepiller <julien@xxxxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: [PATCH]: improved cryptsetup translation for Italian (it)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH]: improved cryptsetup translation for Italian (it)
  • From: Guido Trentalancia <guido@xxxxxxxxxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Ralf Ramsauer <ralf+dm@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Ralf Ramsauer <ralf+dm@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• LUKS is written to a device with no partition table. Is it possible to add a partition table?
  • From: Joe Hillenbrand <joehillen@xxxxxxxxx>
• Re: [PATCH] include sys/sysmacros.h for major/minor/makedev
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: [PATCH] include sys/sysmacros.h for major/minor/makedev
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH] include sys/sysmacros.h for major/minor/makedev
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• [PATCH] include sys/sysmacros.h for major/minor/makedev
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: [PATCH] include sys/sysmacros.h for major/minor/makedev
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• problem with uuid library while cross-compiling for zynq
  • From: "Brandi, Rocco (KHHQ)" <Rocco.Brandi@xxxxxxxxxxxxxxxxxx>
• Re: LUKS1 devmapper device mount issue
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Fuzzing
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Fuzzing
  • From: Lars Winterfeld <lars.winterfeld@xxxxxxxxxxxxx>
• Re: LUKS1 devmapper device mount issue
  • From: Amith Kumar Ramachandra <amitnr@xxxxxxxxx>
• Re: LUKS1 devmapper device mount issue
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS1 devmapper device mount issue
  • From: Amith Kumar Ramachandra <amitnr@xxxxxxxxx>
• Re: LUKS1 devmapper device mount issue
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• LUKS1 devmapper device mount issue
  • From: Amith Kumar Ramachandra <amitnr@xxxxxxxxx>
• Re: Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close
  • From: Guido Trentalancia <guido@xxxxxxxxxxxxxxxx>
• Re: Encrypted container showing only lost+found directory.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Encrypted container showing only lost+found directory.
  • From: Dani <danipozo@xxxxxxxxxxxxx>
• Re: Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close
  • From: Guido Trentalancia <guido@xxxxxxxxxxxxxxxx>
• Re: Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close
  • From: Guido Trentalancia <guido@xxxxxxxxxxxxxxxx>
• Re: Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close
  • From: Guido Trentalancia <guido@xxxxxxxxxxxxxxxx>
• Re: Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close
  • From: Guido Trentalancia <guido@xxxxxxxxxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: Encrypted fs in file
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Encrypted fs in file
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Encrypted fs in file
  • From: Matthias Schniedermeyer <ms@xxxxxxx>
• Encrypted fs in file
  • From: doark@xxxxxxxx
• Re: Failed to setup dm-crypt key mapping for device cryptfile.
  • From: Nicolas Bock <nicolasbock@xxxxxxxxx>
• Re: Quorum system on decryption passphrase
  • From: "Fernando D. Pedemonte" <fernando.pedemonte@xxxxxxxxxxxxxx>
• Re: Quorum system on decryption passphrase
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Quorum system on decryption passphrase
  • From: Selim James Levy <sjtlevy@xxxxxxxxx>
• Re: Quorum system on decryption passphrase
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Quorum system on decryption passphrase
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Quorum system on decryption passphrase
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Quorum system on decryption passphrase
  • From: Fulano Diego Perez <fulanoperez@xxxxxxxxxxxxx>
• Re: Quorum system on decryption passphrase
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Quorum system on decryption passphrase
  • From: "Fernando D. Pedemonte" <fernando.pedemonte@xxxxxxxxxxxxxx>
• Re: Failed to setup dm-crypt key mapping for device cryptfile.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Failed to setup dm-crypt key mapping for device cryptfile.
  • From: yumkam@xxxxxxxxx (Yuriy M. Kaminskiy)
• Failed to setup dm-crypt key mapping for device cryptfile.
  • From: Nicolas Bock <nicolasbock@xxxxxxxxx>
• Re: concurrency
  • From: Hugh Bragg <hughbragg@xxxxxxxxxxx>
• Re: concurrency
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: concurrency
  • From: Hugh Bragg <hughbragg@xxxxxxxxxxx>
• Re: concurrency
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: concurrency
  • From: Hugh Bragg <hughbragg@xxxxxxxxxxx>
• Re: concurrency
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: concurrency
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: concurrency
  • From: Hugh Bragg <hughbragg@xxxxxxxxxxx>
• Re: concurrency
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• concurrency
  • From: Hugh Bragg <hughbragg@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: David Niklas <doark@xxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: David Niklas <doark@xxxxxxxx>
• Re: Some questions/clarifications around the LUKS spec
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Some questions/clarifications around the LUKS spec
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: dm-crypt Digest, Vol 81, Issue 4
  • From: "Sumaya1960@xxxxxx" <Sumaya1960@xxxxxx>
• Re: Some questions/clarifications around the LUKS spec
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Some questions/clarifications around the LUKS spec
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Some questions/clarifications around the LUKS spec
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Some questions/clarifications around the LUKS spec
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Some questions/clarifications around the LUKS spec
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: LUKS NVMe M.2 SSD - save disklayout...
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Some questions/clarifications around the LUKS spec
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: dm-crypt Digest, Vol 81, Issue 2
  • From: "Sumaya1960@xxxxxx" <Sumaya1960@xxxxxx>
• Re: LUKS NVMe M.2 SSD - save disklayout...
  • From: Matthias Schniedermeyer <ms@xxxxxxx>
• Re: LUKS NVMe M.2 SSD - save disklayout...
  • From: doark@xxxxxxxx
• Re: LUKS NVMe M.2 SSD - save disklayout...
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• LUKS NVMe M.2 SSD - save disklayout...
  • From: "Sumaya1960@xxxxxx" <Sumaya1960@xxxxxx>
• [ANNOUNCE] cryptsetup 1.7.1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: help
  • From: Felix Wagner <felix@xxxxxxxxxxxxxxxx>
• Re: help
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: help
  • From: Felix Wagner <felix@xxxxxxxxxxxxxxxx>
• Re: help
  • From: Felix Wagner <felix@xxxxxxxxxxxxxxxx>
• Re: help
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: help
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• help
  • From: Felix Wagner <felix@xxxxxxxxxxxxxxxx>
• Re: help
  • From: Felix Wagner <felix@xxxxxxxxxxxxxxxx>
• Re: help
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: help
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• help
  • From: Felix Wagner <felix@xxxxxxxxxxxxxxxx>
• Re: yet another header reconstruction question
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: yet another header reconstruction question
  • From: "Florian Dotzer" <florian.dotzer@xxxxxx>
• Re: Crypto-changes in some kernels
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Crypto-changes in some kernels
  • From: Michael Strauss <the.whistler@xxxxxxx>
• Re: yet another header reconstruction question
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: yet another header reconstruction question
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: yet another header reconstruction question
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: yet another header reconstruction question
  • From: "Florian Dotzer" <florian.dotzer@xxxxxx>
• Re: yet another header reconstruction question
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: yet another header reconstruction question
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: yet another header reconstruction question
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• yet another header reconstruction question
  • From: "Florian Dotzer" <florian.dotzer@xxxxxx>
• Re: Yet another header reconstruction question
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Yet another header reconstruction question
  • From: "Florian Dotzer" <florian.dotzer@xxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Subscriptions <sub@xxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Subscriptions <sub@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Lars Winterfeld <lars.winterfeld@xxxxxxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Rypervenche <sub@xxxxxxxxx>
• Re: Size of LUKS header and how to overwrite
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Size of LUKS header and how to overwrite
  • From: Rypervenche <sub@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: The future of disk encryption with LUKS2
  • From: Lars Winterfeld <lars.winterfeld@xxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Zaolin <zaolin@xxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: "Sumaya1960@xxxxxx" <Sumaya1960@xxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: The future of disk encryption with LUKS2
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• The future of disk encryption with LUKS2
  • From: ".. ink .." <mhogomchungu@xxxxxxxxx>
• Re: Cross-compile cryptsetup on Android
  • From: Zaolin <zaolin@xxxxxxxxxxxxx>
• Re: Cross-compile cryptsetup on Android
  • From: Ralf Ramsauer <ralf@xxxxxxxxxxxxxxxxxxxxxx>
• Cross-compile cryptsetup on Android
  • From: "shengdexinqing@xxxxxxxxxxx" <shengdexinqing@xxxxxxxxxxx>
• Re: Automatically mount LUKS LVM on boot?
  • From: "Arbiel (gmx)" <arbiel.perlacremaz@xxxxxx>
• Re: Header corrupted?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Header corrupted?
  • From: Sumaya <Sumaya1960@xxxxxx>
• Re: Automatically mount LUKS LVM on boot?
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Automatically mount LUKS LVM on boot?
  • From: Dáire Fagan <dairefagan@xxxxxxxxx>
• Re: Header corrupted?
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Header corrupted?
  • From: David Christensen <dpchrist@xxxxxxxxxxxxxxxx>
• Re: Header corrupted?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Header corrupted?
  • From: "sumaya1960@xxxxxx" <sumaya1960@xxxxxx>
• Header?
  • From: "sumaya1960@xxxxxx" <sumaya1960@xxxxxx>
• Re: Auto mount encrypted partition with passphrase stored in a external driver
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Auto mount encrypted partition with passphrase stored in a external driver
  • From: "Almeida, Gabriel" <Gabriel.Almeida@xxxxxxxxxx>
• Re: Auto mount encrypted partition with passphrase stored in a external driver
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Auto mount encrypted partition with passphrase stored in a external driver
  • From: "Almeida, Gabriel" <Gabriel.Almeida@xxxxxxxxxx>
• Re: change backend for LUKS
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• change backend for LUKS
  • From: Raffaele Brivio <raffaele.brivio@xxxxxxxxx>
• help
  • From: "Eugen Rogoza" <euro123@xxxxxxx>
• Re: Alignment issue with 4K disk
  • From: "Eugen Rogoza" <eugen.rogoza@xxxxxx>
• Re: Alignment issue with 4K disk
  • From: "Eugen Rogoza" <euro123@xxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: "Eugen Rogoza" <euro123@xxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: "Eugen Rogoza" <euro123@xxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: "Eugen Rogoza" <eugen.rogoza@xxxxxx>
• Re: Alignment issue with 4K disk
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: ".. ink .." <mhogomchungu@xxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• Re: Alignment issue with 4K disk
  • From: Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>
• Alignment issue with 4K disk
  • From: Yves-Alexis Perez <corsac@xxxxxxxxxx>
• Re: Variable data offset for a LUKS volume that uses a detached header.
  • From: Arno Wagner <arno@xxxxxxxxxxx>