Device-Mapper Crypto

• Thread Index

• Cryptsetup git main default branch
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: New cryptsetup development list
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• New cryptsetup development list
  • From: Maxim Fomin <maxim@xxxxxxxxx>
• New cryptsetup development list
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: misaligned ending sector, 4096-byte luks sector size can't be used
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: misaligned ending sector, 4096-byte luks sector size can't be used
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: misaligned ending sector, 4096-byte luks sector size can't be used
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: misaligned ending sector, 4096-byte luks sector size can't be used
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: misaligned ending sector, 4096-byte luks sector size can't be used
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: misaligned ending sector, 4096-byte luks sector size can't be used
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• misaligned ending sector, 4096-byte luks sector size can't be used
  • From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
• Re: cryptsetup 2.4.3 (CVE-2021-4122 fix)
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: cryptsetup 2.4.3 (CVE-2021-4122 fix)
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: cryptsetup 2.4.3 (CVE-2021-4122 fix)
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: cryptsetup 2.4.3 (CVE-2021-4122 fix)
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: cryptsetup 2.4.3 (CVE-2021-4122 fix)
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: [ANNOUNCE] cryptsetup 2.3.7 (CVE-2021-4122 fix)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.4.3 (CVE-2021-4122 fix)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.3.7 (CVE-2021-4122 fix)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Is AES-GCM still a bad idea?
  • From: Alex Lieflander <atlief@xxxxxxxxxx>
• Re: Is AES-GCM still a bad idea?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Is AES-GCM still a bad idea?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Is AES-GCM still a bad idea?
  • From: Alex Lieflander <atlief@xxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.4.2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-crypt list mailman dead?
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Opening a LUKS container using a USB drive
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: dm-crypt list mailman dead?
  • From: Jana Saout <jana@xxxxxxxx>
• dm-crypt list mailman dead?
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Opening a LUKS container using a USB drive
  • From: Mikhail Morfikov <mmorfikov@xxxxxxxxx>
• Re: veritysetup and CentOS 8
  • From: "Wei, Catherine" <catherine.wei@xxxxxxxxxxxxx>
• Re: veritysetup and CentOS 8
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [RFC] Partial support for reading DiskCryptor volumes
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [RFC] Partial support for reading DiskCryptor volumes
  • From: Mateusz Jończyk <mat.jonczyk@xxxxxxxxx>
• Re: [RFC] Partial support for reading DiskCryptor volumes
  • From: Mateusz Jończyk <mat.jonczyk@xxxxxxxxx>
• Re: [RFC] Partial support for reading DiskCryptor volumes
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [RFC] Partial support for reading DiskCryptor volumes
  • From: Mateusz Jończyk <mat.jonczyk@xxxxx>
• Re: veritysetup and CentOS 8
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [cryptsetup PATCH] Make BitLocker support optional
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [cryptsetup PATCH] Make BitLocker support optional
  • From: Phil Sutter <phil@xxxxxx>
• [cryptsetup PATCH] Make BitLocker support optional
  • From: Phil Sutter <phil@xxxxxx>
• Re: veritysetup and CentOS 8
  • From: "Wei, Catherine" <catherine.wei@xxxxxxxxxxxxx>
• Re: veritysetup and CentOS 8
  • From: "Wei, Catherine" <catherine.wei@xxxxxxxxxxxxx>
• Re: [cryptsetup PATCH] Make BitLocker support optional
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: reg: Question on LUKS device's content exposure
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: reg: Question on LUKS device's content exposure
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: veritysetup and CentOS 8
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: reg: Question on LUKS device's content exposure
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• reg: Question on LUKS device's content exposure
  • From: sami0l <samsapi01@xxxxxxxxxxxxx>
• veritysetup and CentOS 8
  • From: "Wei, Catherine" <catherine.wei@xxxxxxxxxxxxx>
• Re: Argon2 limits choice
  • From: Dmitry Dmitry <dimanne@xxxxxxxxx>
• Re: Argon2 limits choice
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Argon2 limits choice
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Argon2 limits choice
  • From: Dmitry Dmitry <dimanne@xxxxxxxxx>
• Re: --disable-locks
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: --disable-locks
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• --disable-locks
  • From: Jeremiah Moree <jtmoree@xxxxxxxxx>
• Re: subscribe
  • From: Jeremiah Moree <jtmoree@xxxxxxxxx>
• Re: cryptsetup - 2FA feature request
  • From: Jeremiah Moree <jtmoree@xxxxxxxxx>
• Re: cryptsetup - 2FA feature request
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.4.1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Help with dm-crypt/luks on mediatek device
  • From: Adam Pigg <adam@xxxxxxxxxxx>
• cryptsetup - 2FA feature request
  • From: Stephen Feyrer <stephen.feyrer@xxxxxxxxxxxxxx>
• Re: Is this thing on?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Is this thing on?
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: cryptsetup 2.4.0 does not compile on musl libc anymore
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: json help
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• pdf documentation
  • From: Jeremiah Moree <jtmoree@xxxxxxxxx>
• Re: cryptsetup 2.4.0 does not compile on musl libc anymore
  • From: Sören Tempel <soeren@xxxxxxxxxxxxxxxxx>
• Re: json help
  • From: JT Morée <moreejt@xxxxxxxxx>
• pdf documentation
  • From: JT Morée <moreejt@xxxxxxxxx>
• FAQ update
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: cryptsetup 2.4.0 does not compile on musl libc anymore
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup 2.4.0 does not compile on musl libc anymore
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Sync luks passphrase with LDAP
  • From: Tania Hagan <taniahagan@xxxxxxxxxxxxxx>
• cryptsetup 2.4.0 does not compile on musl libc anymore
  • From: Sören Tempel <soeren@xxxxxxxxxxxxxxxxx>
• cryptsetup 2.4.0 planned release date?
  • From: Frank Heimes <frank.heimes@xxxxxxxxxxxxx>
• Re: [PATCH] dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
  • From: Arne Welzel <arne.welzel@xxxxxxxxxxxxx>
• LUKS keeps asking for password after binding with TPM2
  • From: "W. Miah" <wadud.miah@xxxxxxxxx>
• [PATCH] dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
  • From: Arne Welzel <arne.welzel@xxxxxxxxxxxxx>
• USB Encrypted Drive
  • From: James Johnson <Exaviour_Black@xxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: Samuel Mendoza-Jonas <samjonas@xxxxxxxxxx>
• post-mortem: Encrypted LUKS volume does not accept password on boot after system freeze
  • From: luroc <luroc@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.4.0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: json help
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: json help
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: json help
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: [PATCH] dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: json help
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• json help
  • From: JT Morée <moreejt@xxxxxxxxx>
• AEAD, recommended alogs and some more questions
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: [PATCH] dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• LUKS keeps asking for password after binding with TPM2
  • From: "W. Miah" <wadud.miah@xxxxxxxxx>
• Re: secure use of cryptsetup by non-root
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: secure use of cryptsetup by non-root
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: secure use of cryptsetup by non-root
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: secure use of cryptsetup by non-root
  • From: pg@xxxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: secure use of cryptsetup by non-root
  • From: pg@xxxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: secure use of cryptsetup by non-root
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• secure use of cryptsetup by non-root
  • From: JT Morée <moreejt@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.4.0-rc1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.4.0-rc0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS container creation without device mapper or loop device access
  • From: Yoann CONGAL <yoann.congal@xxxxxxxx>
• Re: LUKS container creation without device mapper or loop device access
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• LUKS container creation without device mapper or loop device access
  • From: Yoann CONGAL <yoann.congal@xxxxxxxx>
• Re: Performance/Requirements of Argon2 header with removable devices
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Combining ciphers with LUKS possible?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Performance/Requirements of Argon2 header with removable devices
  • From: Andreas Heinlein <aheinlein@xxxxxxx>
• Combining ciphers with LUKS possible?
  • From: Andreas Heinlein <aheinlein@xxxxxxx>
• Re: Looking for reverse-engineering partner for DiskCryptor
  • From: Mateusz Jończyk <mat.jonczyk@xxxxx>
• Re: Looking for reverse-engineering partner for DiskCryptor
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Looking for reverse-engineering partner for DiskCryptor
  • From: Mateusz Jończyk <mat.jonczyk@xxxxx>
• [ANNOUNCE] cryptsetup 2.3.6
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS partition creation date
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS partition creation date
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: LUKS partition creation date
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS partition creation date
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS partition creation date
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• LUKS partition creation date
  • From: Valdez <u961866@xxxxxxxxxxxx>
• Re: Luks, use the double force! :)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Luks, use the double force! :)
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Luks, use the double force! :)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Luks, use the double force! :)
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Luks, use the double force! :)
  • From: JAC <xxjacs@xxxxxxxxx>
• Re: last mount time
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• last mount time
  • From: u961866@xxxxxxxxxxxx
• Re: Reading the passphrase from a key-file
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Reading the passphrase from a key-file
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Reading the passphrase from a key-file
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Reading the passphrase from a key-file
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Reading the passphrase from a key-file
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: Changheun Lee <nanich.lee@xxxxxxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Reading the passphrase from a key-file
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Reading the passphrase from a key-file
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Reading the passphrase from a key-file
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Reading the passphrase from a key-file
  • From: Volker Dormeyer <vd@xxxxxxxxxxxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master
  • From: Changheun Lee <nanich.lee@xxxxxxxxxxx>
• Re: Coding/style guidelines for cryptsetup?
  • From: "Schneider, Robert" <robert.schneider03@xxxxxxx>
• Re: Coding/style guidelines for cryptsetup?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Coding/style guidelines for cryptsetup?
  • From: "Schneider, Robert" <robert.schneider03@xxxxxxx>
• Re: Help: problem with an encrypted USB drive
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Help: problem with an encrypted USB drive
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Help: problem with an encrypted USB drive
  • From: pg@xxxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Help: problem with an encrypted USB drive
  • From: Kasperi <kasperikoti@xxxxxxxxxx>
• Re: Transactional updates for LUKS2 metadata?
  • From: "Schneider, Robert" <robert.schneider03@xxxxxxx>
• Re: Antw: [EXT] [systemd-devel] Kdump with full-disk LUKS encryption
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Kdump with full-disk LUKS encryption
  • From: Kairui Song <kasong@xxxxxxxxxx>
• Antw: [EXT] [systemd-devel] Kdump with full-disk LUKS encryption
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Transactional updates for LUKS2 metadata?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Kdump with full-disk LUKS encryption
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Kdump with full-disk LUKS encryption
  • From: Kairui Song <kasong@xxxxxxxxxx>
• Re: Transactional updates for LUKS2 metadata?
  • From: "Schneider, Robert" <robert.schneider03@xxxxxxx>
• Re: Transactional updates for LUKS2 metadata?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Transactional updates for LUKS2 metadata?
  • From: "Schneider, Robert" <robert.schneider03@xxxxxxx>
• Re: Aligning entire LUKS/LVM/Ext4 filesystem stack to 4K sectors
  • From: Erwin van Londen <erwin@xxxxxxxxxxxxxxxxxx>
• Re: [DM-Verity] Corruption after activation during boot
  • From: Aditya Prakash <adiprakash@xxxxxxxxxxxxxxxxx>
• Re: [DM-Verity] Corruption after activation during boot
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [DM-Verity] Corruption after activation during boot
  • From: Aditya Prakash <adiprakash@xxxxxxxxxxxxxxxxx>
• Re: 32/64-bit compatibility: Plain encryption of USB device partition
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• 32/64-bit compatibility: Plain encryption of USB device partition
  • From: Matthias Schwartz <m.schwartz@xxxxxxxxxxxxxx>
• Re: Using dm-crypt: whole disk encryption
  • From: ken <gebser@xxxxxxxxxxxx>
• Re: Aligning entire LUKS/LVM/Ext4 filesystem stack to 4K sectors
  • From: Johnny Dahlberg <svartchimpans@xxxxxxxxx>
• Re: [DM-Verity] Corruption after activation during boot
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [DM-Verity] Corruption after activation during boot
  • From: Tom Eccles <tom.eccles@xxxxxxxxxxxxxxx>
• Re: Using dm-crypt: whole disk encryption
  • From: Johnny Dahlberg <svartchimpans@xxxxxxxxx>
• Re: Is crypttab secure to automount a partition?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: What to encrypt and why (was: Using dm-crypt: whole disk encryption
  • From: Maksim Fomin <maxim@xxxxxxxxx>
• Re: Using dm-crypt: whole disk encryption
  • From: Didier Spaier <didier@xxxxxxxx>
• Re: What to encrypt and why (was: Using dm-crypt: whole disk encryption
  • From: Johnny Dahlberg <svartchimpans@xxxxxxxxx>
• Re: What to encrypt and why (was: Using dm-crypt: whole disk encryption
  • From: Maksim Fomin <maxim@xxxxxxxxx>
• Using dm-crypt: whole disk encryption
  • From: Maksim Fomin <maxim@xxxxxxxxx>
• Re: What to encrypt and why (was: Using dm-crypt: whole disk encryption
  • From: Johnny Dahlberg <svartchimpans@xxxxxxxxx>
• What to encrypt and why (was: Using dm-crypt: whole disk encryption
  • From: ken <gebser@xxxxxxxxxxxx>
• Re: Is crypttab secure to automount a partition?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Using dm-crypt: whole disk encryption
  • From: Johnny Dahlberg <svartchimpans@xxxxxxxxx>
• Re: Is crypttab secure to automount a partition?
  • From: Christopher de Vidal <cbdevidal.jk1@xxxxxxxxx>
• Re: Performance of KVM & guest hosts under DM Crypt?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Password screen configuration
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Using dm-crypt: whole disk encryption
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Password screen configuration
  • From: ken <gebser@xxxxxxxxxxxx>
• Performance of KVM & guest hosts under DM Crypt?
  • From: ken <gebser@xxxxxxxxxxxx>
• Using dm-crypt: whole disk encryption
  • From: ken <gebser@xxxxxxxxxxxx>
• Re: Is crypttab secure to automount a partition?
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Please help!!! GRUB reinstallation messed with LUKS
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Is crypttab secure to automount a partition?
  • From: Christopher de Vidal <cbdevidal.jk1@xxxxxxxxx>
• [DM-Verity] Corruption after activation during boot
  • From: Aditya Prakash <adiprakash@xxxxxxxxxxxxxxxxx>
• Re: Aligning entire LUKS/LVM/Ext4 filesystem stack to 4K sectors
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Aligning entire LUKS/LVM/Ext4 filesystem stack to 4K sectors
  • From: Johnny Dahlberg <svartchimpans@xxxxxxxxx>
• Re: Aligning entire LUKS/LVM/Ext4 filesystem stack to 4K sectors
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Aligning entire LUKS/LVM/Ext4 filesystem stack to 4K sectors
  • From: Johnny Dahlberg <svartchimpans@xxxxxxxxx>
• Aligning entire LUKS/LVM/Ext4 filesystem stack to 4K sectors
  • From: Maksim Fomin <maxim@xxxxxxxxx>
• Aligning entire LUKS/LVM/Ext4 filesystem stack to 4K sectors
  • From: Johnny Dahlberg <svartchimpans@xxxxxxxxx>
• Re: [DM-Verity][HELP] Unlock Verity Target during runtime
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [DM-Verity][HELP] Unlock Verity Target during runtime
  • From: Aditya Prakash <adiprakash@xxxxxxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.3.5
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.3.5-rc0 (release candidate)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Spontaneous Unmounting - LUKS Device Busy
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Spontaneous Unmounting - LUKS Device Busy
  • From: Frederick Gotham <thomas123@xxxxxx>
• Re: How to attached a detached header?
  • From: Volker Dormeyer <vd@xxxxxxxxxxxxxxxx>
• Re: How to attached a detached header?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to attached a detached header?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: How to attached a detached header?
  • From: Volker Dormeyer <vd@xxxxxxxxxxxxxxxx>
• Re: How to attached a detached header?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• How to attached a detached header?
  • From: Volker Dormeyer <vd@xxxxxxxxxxxxxxxx>
• Re: LUKS device failure after Cryptsetup upgrade
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• LUKS device failure after Cryptsetup upgrade
  • From: Maxime Alves <maxime.alves@xxxxxxxx>
• hardware accelerated encryption
  • From: grumpy@xxxxxxxxxxxxx
• Fw: Re: Recover from Spontaneous Ejection
  • From: Frederick Gotham <thomas123@xxxxxx>
• Re: Recover from Spontaneous Ejection
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Recover from Spontaneous Ejection
  • From: Frederick Gotham <thomas123@xxxxxx>
• Re: Recover from Spontaneous Ejection
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Recover from Spontaneous Ejection
  • From: Frederick Gotham <thomas123@xxxxxx>
• [PATCH] dm crypt: fix invalid copy paste in crypt_alloc_req_aead
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [PATCH] dm crypt: defer the decryption to a tasklet, when being called with interrupts disabled
  • From: "Maciej S. Szmigiero" <mail@xxxxxxxxxxxxxxxxxxxxx>
• Re: Help wanted to set up full disk encryption using GRUB
  • From: Martin Jørgensen <mjoerg@xxxxxxxxx>
• Help wanted to set up full disk encryption using GRUB
  • From: Didier Spaier <didier@xxxxxxxx>
• Re: Help wanted to set up full disk encryption using GRUB
  • From: Didier Spaier <didier@xxxxxxxx>
• [PATCH] dm crypt: defer the decryption to a tasklet, when being called with interrupts disabled
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• [PATCH] dm crypt: do not call bio_endio() from the dm-crypt tasklet
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: length of keyfiles
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: length of keyfiles
  • From: Felix Rubio <felix@xxxxxxxxx>
• Re: length of keyfiles
  • From: Felix Rubio <felix@xxxxxxxxx>
• Re: length of keyfiles
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• length of keyfiles
  • From: Felix Rubio <felix@xxxxxxxxx>
• Re: [PATCH v3 0/2] dm crypt: some fixes to support dm-crypt running in softirq context
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v3 2/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• [PATCH v3 1/2] dm crypt: do not wait for backlogged crypto request completion in softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• [PATCH v3 0/2] dm crypt: some fixes to support dm-crypt running in softirq context
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• [PATCH v2 2/2] dm crypt: do not wait for backlogged crypto request completion in softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• [PATCH v2 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v2 0/2] dm crypt: some fixes to support dm-crypt running in softirq context
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• cryptsetup in kubernetes pods
  • From: Shreyas Bapat <shreyas@xxxxxxxx>
• Re: [PATCH 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Hillf Danton <hdanton@xxxxxxxx>
• [PATCH 2/2] dm crypt: do not wait for backlogged crypto request completion in softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• [PATCH 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs scrub = BUG()
  • From: "Maciej S. Szmigiero" <mail@xxxxxxxxxxxxxxxxxxxxx>
• Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs scrub = BUG()
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: FDE with passphrase + low cost HSM in LUKS on boot
  • From: "Fabio Martins" <fm.crypt1@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Question about mounting an external hard drive
  • From: Jorge Fábregas <jorge.fabregas@xxxxxxxxx>
• Question about mounting an external hard drive
  • From: "Dr. David Bower" <dr.david.bower@xxxxxxxxxx>
• Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs scrub = BUG()
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs scrub = BUG()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs scrub = BUG()
  • From: "Maciej S. Szmigiero" <mail@xxxxxxxxxxxxxxxxxxxxx>
• Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs scrub = BUG()
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: FDE with passphrase + low cost HSM in LUKS on boot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs scrub = BUG()
  • From: "Maciej S. Szmigiero" <mail@xxxxxxxxxxxxxxxxxxxxx>
• Re: FDE with passphrase + low cost HSM in LUKS on boot
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: FDE with passphrase + low cost HSM in LUKS on boot
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Dm-crypt list archive on lore.kernel.org
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Creating a LUKS container with a pre-made Argon hash
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS2 SSD swap and system freeze
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• FDE with passphrase + low cost HSM in LUKS on boot
  • From: "Fabio Martins" <fm.crypt1@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Properly enabling TRIM for dm-crypt on an SSD
  • From: Mistave <mistave@xxxxxxxxxxxxxxx>
• Re: Properly enabling TRIM for dm-crypt on an SSD
  • From: Mistave <mistave@xxxxxxxxxxxxxxx>
• Re: Properly enabling TRIM for dm-crypt on an SSD
  • From: Martin Jørgensen <mjoerg@xxxxxxxxx>
• Properly enabling TRIM for dm-crypt on an SSD
  • From: Mistave <mistave@xxxxxxxxxxxxxxx>
• Re: cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
  • From: Martin Jørgensen <mjoerg@xxxxxxxxx>
• Re: LUKS2 SSD swap and system freeze
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• LUKS2 SSD swap and system freeze
  • From: Germano Massullo <germano.massullo@xxxxxxxxx>
• Re: Keyboard map issue
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• dm-crypt with no_read_workqueue and no_write_workqueue + btrfs scrub = BUG()
  • From: "Maciej S. Szmigiero" <mail@xxxxxxxxxxxxxxxxxxxxx>
• Keyboard map issue
  • From: Bruno Parga <brunoparga@xxxxxxxxx>
• Creating a LUKS container with a pre-made Argon hash
  • From: "Misha Gusarov" <dottedmag@xxxxxxxxxxxxx>
• Error Message - Could someone give me a pointer?
  • From: Diagon <saout.boxy@xxxxxxxx>
• veritysetup usage question
  • From: Jan Pohanka <xhpohanka@xxxxxxxxx>
• Re: cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
  • From: Martin Jørgensen <mjoerg@xxxxxxxxx>
• dm-verity performance improvements
  • From: Riz <mdrizwan827@xxxxxxxxx>
• Re: cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
  • From: Martin Jørgensen <mjoerg@xxxxxxxxx>
• Re: cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
  • From: Martin Jørgensen <mjoerg@xxxxxxxxx>
• Re: How to remove LUKS encryption
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• How to remove LUKS encryption
  • From: Anar Məsimli <anar.masimov@xxxxxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: Davide Marchi <danjde@xxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: Davide Marchi <danjde@xxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: Davide Marchi <danjde@xxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: unlock via password and device
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Encrypting DVD or CDROM from iso
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Encrypting DVD or CDROM from iso
  • From: Davide Marchi <danjde@xxxxxx>
• unlock via password and device
  • From: "chiasa.men" <chiasa.men@xxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Jörg Kastning <joerg.kastning@xxxxxxxxxxxxxx>
• cryptsetup hangs on "waiting for zero"
  • From: 0xffce <0xffce@xxxxxxxxxxxxxx>
• Re: cryptsetup hangs on "waiting for zero"
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• cryptsetup hangs on "waiting for zero"
  • From: 0xffce <0xffce@xxxxxxxxxxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Jörg Kastning <joerg.kastning@xxxxxxxxxxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Jörg Kastning <joerg.kastning@xxxxxxxxxxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Jörg Kastning <joerg.kastning@xxxxxxxxxxxxxx>
• Re: Do you accept contributions to manpage via patch?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Do you accept contributions to manpage via patch?
  • From: Jörg Kastning <joerg.kastning@xxxxxxxxxxxxxx>
• Re: SSD encryption using cryptsetup
  • From: KRISHNAJA MENON <krishnajamenon92@xxxxxxxxx>
• Re: Regarding DAS Encryption for RHEL7
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: SSD encryption using cryptsetup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Opening container created on aarch64 fails on x86_64 and the other way around; was: SSD encryption using cryptsetup
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• SSD encryption using cryptsetup
  • From: KRISHNAJA MENON <krishnajamenon92@xxxxxxxxx>
• Regarding DAS Encryption for RHEL7
  • From: La Poubelle <logan82097laboube@xxxxxxxxx>
• Re: Help with dm-crypt/luks on mediatek device
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Help with dm-crypt/luks on mediatek device
  • From: Adam Pigg <adam@xxxxxxxxxxx>
• Re: [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: bug in cryptsetup --header option when using luksFormat?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Sudhakar Panneerselvam <sudhakar.panneerselvam@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Sudhakar Panneerselvam <sudhakar.panneerselvam@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Sudhakar Panneerselvam <sudhakar.panneerselvam@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Sudhakar Panneerselvam <sudhakar.panneerselvam@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Sudhakar Panneerselvam <sudhakar.panneerselvam@xxxxxxxxxx>
• Re: [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Sudhakar Panneerselvam <sudhakar.panneerselvam@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Sudhakar Panneerselvam <sudhakar.panneerselvam@xxxxxxxxxx>
• Re: [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Sudhakar Panneerselvam <sudhakar.panneerselvam@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/2] dm crypt: Allow unaligned buffer lengths for skcipher devices
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: how to debug cryptsetup with gdb?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• how to debug cryptsetup with gdb?
  • From: Keith Broerman <keith.broerman@xxxxxxxxx>
• Re: LUKS Root Volume encryption.
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: How to debug the start up process ?
  • From: su <su_cj81@xxxxxxx>
• Re: How to debug the start up process ?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• How to debug the start up process ?
  • From: su <su_cj81@xxxxxxx>
• LUKS Root Volume encryption.
  • From: Dev Chakraborty <ujjwaldev003@xxxxxxxxx>
• luksAddKey one liner
  • From: Frederick Gotham <thomas123@xxxxxx>
• one-liner for crypsetup luksAddKey
  • From: Frederick Gotham <thomas123@xxxxxx>
• [ANNOUNCE] cryptsetup 2.3.4
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Full Disk Encryption Systemd
  • From: Nodøn <me@xxxxxxxxxx>
• Re: Encryption speed and reversing the direction
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: Encryption speed and reversing the direction
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Encryption speed and reversing the direction
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Encryption speed and reversing the direction
  • From: John Lee McMahon <john.lee.mcmahon@xxxxxxxxx>
• Re: LUKS2 online reencryption with PAES cipher ?
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: LUKS2 online reencryption with PAES cipher ?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: LUKS2 online reencryption with PAES cipher ?
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• LUKS2 online reencryption with PAES cipher ?
  • From: Ingo Franzki <ifranzki@xxxxxxxxxxxxx>
• Re: Unattended generation/opening.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Unattended generation/opening.
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Unattended generation/opening.
  • From: Diagon <saout.boxy@xxxxxxxx>
• Re: Using dm-verity+dm-crypt on rootfs (Embedded Linux)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Using dm-verity+dm-crypt on rootfs (Embedded Linux)
  • From: Andrii Voloshyn <a.voloshyn@xxxxxxxxxxxxxxxx>
• IO performance implications using dm-crypt
  • From: Erwin van Londen <erwin@xxxxxxxxxxxxxxxxxx>
• Re: Attaching loopback device failed
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Attaching loopback device failed
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: cryptsetup: luksFormat: requires <device> as arguments
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• cryptsetup: luksFormat: requires <device> as arguments
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: Cryptsetup FAQ is confusing re: key-file length and newlines
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Cryptsetup FAQ is confusing re: key-file length and newlines
  • From: John Wiersba <jrw32982@xxxxxxxxx>
• Creating FEC data on the same device
  • From: Riz <mdrizwan827@xxxxxxxxx>
• Re: LUKS passphrase question
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• LUKS passphrase question
  • From: adam peterson <adamjp@xxxxxxxxxxx>
• Re: LuksOpen hangs ?
  • From: B&A Consultants <infos+dmcrypt@xxxxxxxxxxxxxxxxx>
• Re: SparesMissing event on /dev/md4:nsa320 (fwd)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• SparesMissing event on /dev/md4:nsa320 (fwd)
  • From: grumpy@xxxxxxxxxxxxx
• Re: [PATCH v3] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Bob Liu <bob.liu@xxxxxxxxxx>
• Re: [PATCH v3] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: Help request
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Help request
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Help request
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: [dm-devel] [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• [PATCH v3] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Help request
  • From: lacedaemonius <lacedaemonius1@xxxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Bob Liu <bob.liu@xxxxxxxxxx>
• Re: [dm-devel] [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [dm-devel] [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Nobuto Murata <nobuto.murata@xxxxxxxxxxxxx>
• Re: [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: LuksOpen hangs ?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Need some advices on LUKS2 cryptsetup (performance issue with integrity)
  • From: laurent cop <laurent.cop@xxxxxxxxx>
• Re: couple of questions related to using crypto map
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• couple of questions related to using crypto map
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• [PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• LuksOpen hangs ?
  • From: B&A Consultants <infos+dmcrypt@xxxxxxxxxxxxxxxxx>
• DM-integrity questions, a storage-stack plan with request for critique/feedback
  • From: Abe <abe149@xxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [dm-devel] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [dm-devel] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [dm-devel] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Damien Le Moal <Damien.LeMoal@xxxxxxx>
• Re: [dm-devel] [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: How many errors can be corrected by FEC? ( DM-verity)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• How many errors can be corrected by FEC? ( DM-verity)
  • From: Riz <mdrizwan827@xxxxxxxxx>
• Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
  • From: moreejt@xxxxxxxxx
• Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
  • From: d.eltzner@xxxxxx
• Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
  • From: d.eltzner@xxxxxx
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• FEC: Error correction happens only on the verity devive
  • From: Riz <mdrizwan827@xxxxxxxxx>
• [RFC PATCH 0/1] dm-crypt excessive overhead
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
  • From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
• Re: bug in cryptsetup --header option when using luksFormat?
  • From: aral <aral@xxxxxx>
• Re: bug in cryptsetup --header option when using luksFormat?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• bug in cryptsetup --header option when using luksFormat?
  • From: aral@xxxxxx
• Re: can`t build "cryptsetup" release :-(
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• can`t build "cryptsetup" release :-(
  • From: Abe ​ <Abe_the_software_engineer@xxxxxxxxxxx>
• Clarifications 2 to URGENT Help needed w LUKS on KDE Neon
  • From: qelpp <qelpp@xxxxxxxxxxxxxx>
• Update-Clarifications to URGENT Help needed w LUKS on KDE Neon
  • From: qelpp <qelpp@xxxxxxxxxxxxxx>
• URGENT Help needed w LUKS on KDE Neon
  • From: qelpp <qelpp@xxxxxxxxxxxxxx>
• Re: Understanding of --integrity* parameters for LUKS-independent dm-integrity setup
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.3.3
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Understanding of --integrity* parameters for LUKS-independent dm-integrity setup
  • From: asmqb7 <asmqb7@xxxxxxxxx>
• Re: FAQ :WAS: LUKS2 on disk format
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS2 on disk format
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• LUKS2 on disk format
  • From: Maksim Fomin <maxim@xxxxxxxxx>
• Re: LUKS2 on disk format
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• LUKS2 on disk format
  • From: Maksim Fomin <maxim@xxxxxxxxx>
• FAQ :WAS: LUKS2 on disk format
  • From: JT <moreejt@xxxxxxxxx>
• Re: LUKS2 on disk format
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• LUKS2 on disk format
  • From: Maksim Fomin <maxim@xxxxxxxxx>
• luks2 and discard/trim not working
  • From: Nikolay Kichukov <nikolay@xxxxxxxxx>
• Re: luks2 and discard/trim not working
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: luks2 and discard/trim not working
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: luks2 and discard/trim not working
  • From: Nikolay Kichukov <hijacker@xxxxxxxxx>
• Re: luks2 and discard/trim not working
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: luks2 and discard/trim not working
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: luks2 and discard/trim not working
  • From: Nikolay Kichukov <hijacker@xxxxxxxxx>
• Re: luks2 and discard/trim not working
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• luks2 and discard/trim not working
  • From: Nikolay Kichukov <hijacker@xxxxxxxxx>
• Re: Restored luks2 header to wrong drive!
  • From: Default User <hunguponcontent@xxxxxxxxx>
• Re: Restored luks2 header to wrong drive!
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Restored luks2 header to wrong drive!
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Restored luks2 header to wrong drive!
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
• Re: Restored luks2 header to wrong drive!
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Restored luks2 header to wrong drive!
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Restored luks2 header to wrong drive!
  • From: Default User <hunguponcontent@xxxxxxxxx>
• Re: Restored luks2 header to wrong drive!
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Restored luks2 header to wrong drive!
  • From: Default User <hunguponcontent@xxxxxxxxx>
• Re: cryptsetup gui
  • From: grumpy@xxxxxxxxxxxxx
• Re: cryptsetup gui
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup gui
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• cryptsetup gui
  • From: grumpy@xxxxxxxxxxxxx
• [ANNOUNCE] cryptsetup 2.3.2
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: FAQ rework for LUKS2: First pass done
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Some Q&A about LUKS2 reencryption
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Some Q&A about LUKS2 reencryption
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: FAQ rework for LUKS2: First pass done
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: Some Q&A about LUKS2 reencryption
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Some Q&A about LUKS2 reencryption
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• FAQ rework for LUKS2: First pass done
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Adding a drive, and OS
  • From: Suresh Govindachar <sgovindachar@xxxxxxxxx>
• Re: SVG of LUKS icon
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: SVG of LUKS icon
  • From: JT Moree <moreejt@xxxxxxxxx>
• Re: SVG of LUKS icon
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• SVG of LUKS icon
  • From: "Logan Marchione" <logan@xxxxxxxxxxxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Dan Farrell <djfarrell@xxxxxxxxx>
• Re: LUKS FAQ separate for LUKS1/LUKS2, or combined? Was: cryptsetup Yubikey challenge-response support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Dan Farrell <djfarrell@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Dan Farrell <djfarrell@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Dan Farrell <djfarrell@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS FAQ separate for LUKS1/LUKS2, or combined? Was: cryptsetup Yubikey challenge-response support
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS FAQ separate for LUKS1/LUKS2, or combined? Was: cryptsetup Yubikey challenge-response support
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: JT Moree <moreejt@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: JT Moree <moreejt@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Dan Farrell <djfarrell@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Dan Farrell <djfarrell@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Tim Steiner <t@xxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: Nikolay Kichukov <hijacker@xxxxxxxxx>
• Re: cryptsetup Yubikey challenge-response support
  • From: 7heo <7heo@xxxxxxxx>
• cryptsetup Yubikey challenge-response support
  • From: Dan Farrell <djfarrell@xxxxxxxxx>
• Re: unbound keys
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: unbound keys
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: unbound keys
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: unbound keys
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: unbound keys
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: unbound keys
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: bits vs bytes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: unbound keys
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: unbound keys
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: bits vs bytes
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: bits vs bytes
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: bits vs bytes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: bits vs bytes
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: bits vs bytes
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: bits vs bytes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: bits vs bytes
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• unbound keys
  • From: JT Morée <moreejt@xxxxxxxxx>
• bits vs bytes
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: Why is the chk_luks_keyslots tool not routinely included?
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Why is the chk_luks_keyslots tool not routinely included?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Why is the chk_luks_keyslots tool not routinely included?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Why is the chk_luks_keyslots tool not routinely included?
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Re: Why is the chk_luks_keyslots tool not routinely included?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Why is the chk_luks_keyslots tool not routinely included?
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: [Inquire about plain dm-crypt]
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [Inquire about plain dm-crypt]
  • From: "Yoo-Seung Won (Dr)" <yooseung.won@xxxxxxxxxx>
• Re: [Inquire about plain dm-crypt]
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [Inquire about plain dm-crypt]
  • From: "Yoo-Seung Won (Dr)" <yooseung.won@xxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.3.1
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS2 AES-GCM-random erroring with key size issue.
  • From: vinay paduru <vinay.paduru@xxxxxxxx>
• Re: Why OVA size increases after encryption?
  • From: Manish Upasani <manishupasani@xxxxxxxxx>
• Re: Why OVA size increases after encryption?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Why OVA size increases after encryption?
  • From: Max Zettlmeißl <max@xxxxxxxxxxxxxx>
• Re: Why OVA size increases after encryption?
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Why OVA size increases after encryption?
  • From: Manish Upasani <manishupasani@xxxxxxxxx>
• Re: LUKS2 AES-GCM-random erroring with key size issue.
  • From: vinay paduru <vinay.paduru@xxxxxxxx>
• Re: LUKS2 AES-GCM-random erroring with key size issue.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS header and token
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: LUKS2 AES-GCM-random erroring with key size issue.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS header and token
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: LUKS2 AES-GCM-random erroring with key size issue.
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• LUKS2 AES-GCM-random erroring with key size issue.
  • From: vinay paduru <vinay.paduru@xxxxxxxx>
• LUKS header and token
  • From: JT Morée <moreejt@xxxxxxxxx>
• Re: Bug in cryptsetup 2.3.0 (BitLocker key-file support)
  • From: Quentin Lefebvre <qlefebvre_pro@xxxxxxxxx>
• Re: Bug in cryptsetup 2.3.0 (BitLocker key-file support)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Bug in cryptsetup 2.3.0 (BitLocker key-file support)
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Bug in cryptsetup 2.3.0 (BitLocker key-file support)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Bug in cryptsetup 2.3.0 (BitLocker key-file support)
  • From: Quentin Lefebvre <qlefebvre_pro@xxxxxxxxx>
• Re: Bug in cryptsetup 2.3.0 (BitLocker key-file support)
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Bug in cryptsetup 2.3.0 (BitLocker key-file support)
  • From: Quentin Lefebvre <qlefebvre_pro@xxxxxxxxx>
• Re: Streaming ciphers
  • From: Matthias Schniedermeyer <ms@xxxxxxx>
• Re: Streaming ciphers
  • From: David Niklas <doark@xxxxxxxx>
• Re: Streaming ciphers
  • From: Matthias Schniedermeyer <ms@xxxxxxx>
• Re: Streaming ciphers
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Streaming ciphers
  • From: David Niklas <doark@xxxxxxxx>
• Re: Expanding a LUKS partition to a second drive.
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Expanding a LUKS partition to a second drive.
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Expanding a LUKS partition to a second drive.
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Expanding a LUKS partition to a second drive.
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: Expanding a LUKS partition to a second drive.
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Expanding a LUKS partition to a second drive.
  • From: James Dehnert <zeke.dehnert@xxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.3.0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: how to get keyslog PBKDF settings via libcryptsetup
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: how to get keyslog PBKDF settings via libcryptsetup
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Superblock size calculation
  • From: "EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)" <external.Sharmila.D@xxxxxxxxxxxx>
• Re: Data corruption of encrypted partition
  • From: "EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)" <external.Sharmila.D@xxxxxxxxxxxx>
• Re: IV generation for dm-crypt
  • From: "EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)" <external.Sharmila.D@xxxxxxxxxxxx>
• Re: how to get keyslog PBKDF settings via libcryptsetup
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: IV generation for dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: how to get keyslog PBKDF settings via libcryptsetup
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: how to get keyslog PBKDF settings via libcryptsetup
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: how to get keyslog PBKDF settings via libcryptsetup
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: IV generation for dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• IV generation for dm-crypt
  • From: "EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)" <external.Sharmila.D@xxxxxxxxxxxx>
• IV generation in dm-crypt using dmsetup
  • From: "EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)" <external.Sharmila.D@xxxxxxxxxxxx>
• how to get keyslog PBKDF settings via libcryptsetup
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• [ANNOUNCE] cryptsetup 2.3.0-rc0
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Request on support of SM3 and SM4
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Request on support of SM3 and SM4
  • From: "huxiaoyu@xxxxxxxxxxxx" <huxiaoyu@xxxxxxxxxxxx>
• Re: Request on support of SM3 and SM4
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Request on support of SM3 and SM4
  • From: "huxiaoyu@xxxxxxxxxxxx" <huxiaoyu@xxxxxxxxxxxx>
• Re: How to compress LUKS2 header?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to compress LUKS2 header?
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: How to compress LUKS2 header?
  • From: "Julio Cesar Faracco - jfaracco@xxxxxxxxxx" <jfaracco@xxxxxxxxxx>
• Re: How to compress LUKS2 header?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to compress LUKS2 header?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: How to compress LUKS2 header?
  • From: ken <gebser@xxxxxxxxxxxx>
• Re: How to compress LUKS v2 header?
  • From: "Julio Cesar Faracco - jfaracco@xxxxxxxxxx" <jfaracco@xxxxxxxxxx>
• Re: Can't decrypt LUKS partition
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: How to compress LUKS v2 header?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Can't decrypt LUKS partition
  • From: H McCurdy <hmccurdy@xxxxxxxxx>
• Re: Can't decrypt LUKS partition
  • From: H McCurdy <hmccurdy@xxxxxxxxx>
• How to compress LUKS2 header?
  • From: Julio Faracco <jcfaracco@xxxxxxxxx>
• Re: How to compress LUKS v2 header?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Can't decrypt LUKS partition
  • From: <robert.wender@xxxxxxxxxxx>
• How to compress LUKS2 header?
  • From: "Julio Cesar Faracco - jfaracco@xxxxxxxxxx" <jfaracco@xxxxxxxxxx>
• How to compress LUKS v2 header?
  • From: "Julio Cesar Faracco - jfaracco@xxxxxxxxxx" <jfaracco@xxxxxxxxxx>
• Re: Detached header creation confusion.
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Detached header creation confusion.
  • From: Aint Tellin <bdbasstech@xxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Jordan Glover <Golden_Miller83@xxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Robert Nichols <rnicholsNOSPAM@xxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: veritysetup format without --salt
  • From: gilmore@xxxxxxxxxxxxxx
• Re: LUKS2 support for null/plaintext target
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: veritysetup format without --salt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• veritysetup format without --salt
  • From: gilmore@xxxxxxxxxxxxxx
• 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: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anyone know why I can't access my volumes?
  • From: Philipp Rösch <philipp@xxxxx>
• Re: Suddenly unable to access encrypted LUKS partition
  • From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
• Re: Suddenly unable to access encrypted LUKS partition
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Suddenly unable to access encrypted LUKS partition
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Suddenly unable to access encrypted LUKS partition
  • From: ampica@xxxxxxxxxxxxxx
• Re: LUKS2 support for null/plaintext target
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: LUKS2 support for null/plaintext target
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• LUKS2 support for null/plaintext target
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: detached LUKS header size
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: detached LUKS header size
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: detached LUKS header size
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: detached LUKS header size
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: detached LUKS header size
  • From: Michael Kjörling <michael@xxxxxxxxxxx>
• Re: detached LUKS header size
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: detached LUKS header size
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: detached LUKS header size
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: Upper ASCII password shenanigans
  • From: Max Zettlmeißl <max@xxxxxxxxxxxxxx>
• Upper ASCII password shenanigans
  • From: Defiant <mistave@xxxxxxxxxxxxxxx>
• Re: detached LUKS header size
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: detached LUKS header size
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• detached LUKS header size
  • From: Fourhundred Thecat <400thecat@xxxxxx>
• Re: Two questions
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Two questions
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: Two questions
  • From: mgreger@xxxxxxxxxxxx
• Re: Two questions
  • From: mgreger@xxxxxxxxxxxx