Device-Mapper Crypto

• Thread Index

• Re: feature request: findLuksKeySlots
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• feature request: findLuksKeySlots
  • From: Lars Täuber <lars.taeuber@xxxxxxx>
• Re: Re: recent kernels can't access my encrypted disk
  • From: Mathieu SEGAUD <mathieu.segaud@xxxxxxxxx>
• Re: recent kernels can't access my encrypted disk
  • From: "James R. Van Zandt" <jrvz@xxxxxxxxxxx>
• Re: harddrive I/O error, badblocks
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: harddrive I/O error, badblocks
  • From: Heinz Diehl <htd@xxxxxxxxxxxxxxxxx>
• Re: recent kernels can't access my encrypted disk
  • From: Uwe Menges <uwe.menges@xxxxxx>
• Re: harddrive I/O error, badblocks
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: recent kernels can't access my encrypted disk
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• harddrive I/O error, badblocks
  • From: "Marwin M. Butcher" <mg2019av@xxxxxxxxxx>
• recent kernels can't access my encrypted disk
  • From: "James R. Van Zandt" <jrvz@xxxxxxxxxxx>
• Re: Re: cannot format a secondary partirtion with luks
  • From: Marco Giusti <marco.giusti@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Heinz Diehl <htd@xxxxxxxxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: "Nicodemo Alvaro" <nicodemo.alvaro@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Sami Liedes <sliedes@xxxxxxxxx>
• Re: Re: cannot format a secondary partirtion with luks
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Re: cannot format a secondary partirtion with luks
  • From: "Nicodemo Alvaro" <nicodemo.alvaro@xxxxxxxxx>
• Re: cannot format a secondary partirtion with luks
  • From: Dick Middleton <gmane@xxxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: "Clayton Shepard" <cws@xxxxxxxx>
• Re: cannot format a secondary partirtion with luks
  • From: Marco Giusti <marco.giusti@xxxxxxxxx>
• Re: luks encryption with gpg2 key
  • From: Mick Reed <oregon.mick@xxxxxxxxx>
• Re: Journalled FS over LUKS encrypted volume
  • From: Oleg Osovitskiy <oleg@xxxxxxx>
• Re: cannot format a secondary partirtion with luks
  • From: Marco Giusti <marco.giusti@xxxxxxxxx>
• Re: Journalled FS over LUKS encrypted volume
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Journalled FS over LUKS encrypted volume
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Journalled FS over LUKS encrypted volume
  • From: Oleg Osovitskiy <oleg@xxxxxxx>
• [E3E-2A1] cannot format a secondary partirtion with luks
  • From: Marco Giusti <marco.giusti@xxxxxxxxx>
• cannot format a secondary partirtion with luks
  • From: Marco Giusti <marco.giusti@xxxxxxxxx>
• luks encryption with gpg2 key
  • From: "Nicodemo Alvaro" <nicodemo.alvaro@xxxxxxxxx>
• Re: partition table problem
  • From: nicolas@xxxxxxxxxxxxxxxxx
• Re: luksClose: what does it do?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• luksClose: what does it do?
  • From: justin <justin.brown1.1@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: "Antonio De Leon" <aldleonm@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Mick Reed <oregon.mick@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Sami Liedes <sliedes@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: security for failed removal of crypt device?
  • From: Mathieu SEGAUD <mathieu.segaud@xxxxxxxxx>
• Re: security for failed removal of crypt device?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: security for failed removal of crypt device?
  • From: smallnow <smallnow@xxxxxxxxx>
• Re: security for failed removal of crypt device?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• partition table problem
  • From: nicolas@xxxxxxxxxxxxxxxxx
• security for failed removal of crypt device?
  • From: Ian Kelling <ianowl@xxxxxxxxx>
• Re: Off Disk LUKS Header
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Michael Gebetsroither <gebi@xxxxxxxxxxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: Jan Reusch <jreusch@xxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Michael Gebetsroither <gebi@xxxxxxxxxxxxxx>
• Off Disk LUKS Header
  • From: "Clayton Shepard" <cwshep@xxxxxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: "Clayton Shepard" <cwshep@xxxxxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: Mick Reed <oregon.mick@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Michael Gebetsroither <gebi@xxxxxxxxxxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: Sami Liedes <sliedes@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Sami Liedes <sliedes@xxxxxxxxx>
• Re: Re: Request for Comments: Pledge fund for multicore support
  • From: "Clayton Shepard" <cwshep@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Michael Gebetsroither <gebi@xxxxxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Michael Gebetsroither <gebi@xxxxxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Andrew Miklas <public@xxxxxxx>
• Re: SPAM: LOW * re: [dm-crypt] Request for Comments: Pledge fund for multicoresupport
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• SPAM: LOW * re: [dm-crypt] Request for Comments: Pledge fund for multicoresupport
  • From: 杨木祥 <yangmuxiang@xxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Sami Liedes <sliedes@xxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Sami Liedes <sliedes@xxxxxxxxx>
• Re: cryptsetup repository/website change
  • From: "Clayton Shepard" <cwshep@xxxxxxxxx>
• cryptsetup repository/website change
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Request for Comments: Pledge fund for multicore support
  • From: Dave Patterson <sdpatt2@xxxxxxxxx>
• Request for Comments: Pledge fund for multicore support
  • From: Sami Liedes <sliedes@xxxxxxxxx>
• Luks header trouble, luks without header works?
  • From: Jan Marc Hoffmann <exelnet@xxxxxxxxxx>
• Re: [Bug 267192] [NEW] Misleading cryptsetup error message
  • From: Colin Watson <cjwatson@xxxxxxxxxx>
• [FEA-REQ] We want vmpc!
  • From: "Tomasz Sieprawski" <tsieprawski@xxxxxxxxx>
• Re: Re: [Bug 267192] [NEW] Misleading cryptsetup error message [PATCH]
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: [Bug 267192] [NEW] Misleading cryptsetup error message
  • From: Reinhard Tartler <siretart@xxxxxxxxxx>
• Re: [RFC PATCH] cryptsetup: replace udevsettle calls with temporary device error remapping
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Multicore Support?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Multicore Support?
  • From: Chris <cmicel1@xxxxxxxxxxx>
• Re: [RFC PATCH] cryptsetup: replace udevsettle calls with temporary device error remapping
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: [RFC PATCH] cryptsetup: replace udevsettle calls with temporary device error remapping
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: [RFC PATCH] cryptsetup: replace udevsettle calls with temporary device error remapping
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Multicore Support?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Multicore Support?
  • From: Sami Liedes <sliedes@xxxxxxxxx>
• Re: Multicore Support?
  • From: Mathieu SEGAUD <mathieu.segaud@xxxxxxxxx>
• Re: Re: [Bug 267192] [NEW] Misleading cryptsetup error message
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Re: [Bug 267192] [NEW] Misleading cryptsetup error message
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: [Bug 267192] [NEW] Misleading cryptsetup error message
  • From: Reinhard Tartler <siretart@xxxxxxxxxx>
• Re: Multicore Support?
  • From: "Clayton Shepard" <cwshep@xxxxxxxxx>
• Re: Multicore Support?
  • From: "Clayton Shepard" <cws@xxxxxxxx>
• Multicore Support?
  • From: Andrew Miklas <andrew@xxxxxxx>
• [RFC PATCH] cryptsetup: replace udevsettle calls with temporary device error remapping
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• [PATCH] cryptsetup: fix close device in ctrl+c handler
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• [micah@xxxxxxxxxx: [pkg-cryptsetup-devel] Bug#494584: efficacy of xts over 1TB]
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• LUKS and fingerprint scanner identification
  • From: bernd.speiser@xxxxxxxxxxx (Bernd Speiser)
• Re: Massive Failure
  • From: "Clayton Shepard" <cws@xxxxxxxx>
• Selfcorrupted header again, but...
  • From: Martin Nihlberg <martin.nihlberg@xxxxxxxx>
• Latent bug [patch]
  • From: spammed <spammed@xxxxxxxxxx>
• Feature request: Changing the UUID of a LUKS device [patch]
  • From: spammed <spammed@xxxxxxxxxx>
• Re: Re: A12-140 Piping two gpg'ed keys to cryptsetup luksAddKey
  • From: Mick Reed <oregon.mick@xxxxxxxxx>
• [PATCH] Improve error checks when generating LUKS master key
  • From: Erik Edin <erikedin@xxxxxx>
• Re: Re: A12-140 Piping two gpg'ed keys to cryptsetup luksAddKey
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
• Re: A12-140 Piping two gpg'ed keys to cryptsetup luksAddKey
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: Massive Failure
  • From: "Clayton Shepard" <cws@xxxxxxxx>
• Re: Massive Failure
  • From: Roscoe <eocsor@xxxxxxxxx>
• Massive Failure
  • From: "Clayton Shepard" <cws@xxxxxxxx>
• Piping in keys
  • From: Mick Reed <oregon.mick@xxxxxxxxx>
• A12-140 Piping two gpg'ed keys to cryptsetup luksAddKey
  • From: Mick Reed <oregon.mick@xxxxxxxxx>
• Piping two gpg'ed keys to cryptsetup luksAddKey
  • From: Mick Reed <oregon.mick@xxxxxxxxx>
• "Universal" keyscript for LVM encrypted systems with key on removable device
  • From: Swâmi Petaramesh <swami@xxxxxxxxxxxxxx>
• Re: Where is the newest source for cryptsetup?
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Where is the newest source for cryptsetup?
  • From: spammed <spammed@xxxxxxxxxx>
• Re: Any way to integrate Microsoft PKI into dm-crypt?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Any way to integrate Microsoft PKI into dm-crypt?
  • From: "Thomas Cameron (Red Hat)" <tcameron@xxxxxxxxxx>
• Re: Any way to integrate Microsoft PKI into dm-crypt?
  • From: wof <Wolfgang.Aigner@xxxxxx>
• Any way to integrate Microsoft PKI into dm-crypt?
  • From: "Thomas Cameron (Red Hat)" <tcameron@xxxxxxxxxx>
• Re: debian on a crypted pen drive boot in windows
  • From: Adam@xxxxxxxxxxxxx
• Re: debian on a crypted pen drive boot in windows
  • From: wof <Wolfgang.Aigner@xxxxxx>
• Re: debian on a crypted pen drive boot in windows
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• debian on a crypted pen drive boot in windows
  • From: "gabriele esposito" <sickuser@xxxxxxxxx>
• Re: Does dm-crypt support multi-core operations like Truecrypt 6.0 does?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Does dm-crypt support multi-core operations like Truecrypt 6.0 does?
  • From: Jason Haar <Jason.Haar@xxxxxxxxxxxxx>
• Re: LUKS Question
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: LUKS Question
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: LUKS Question
  • From: "Rense Buijen" <rense.buijen@xxxxxxxxx>
• Re: LUKS Question
  • From: Mathieu SEGAUD <mathieu.segaud@xxxxxxxxx>
• Re: LUKS Question
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• RE: LUKS Question
  • From: "Rense Buijen" <rense.buijen@xxxxxxxxx>
• Re: LUKS Question
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• RE: LUKS Question
  • From: "Rense Buijen" <rense.buijen@xxxxxxxxx>
• Re: LUKS Question
  • From: "Ma Begaj" <derliebegott@xxxxxxxxx>
• Re: LUKS Question
  • From: "Rense Buijen" <rense.buijen@xxxxxxxxx>
• Re: LUKS Question
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• LUKS Question
  • From: "Rense Buijen" <rense.buijen@xxxxxxxxx>
• Re: Persistence memory attack
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Persistence memory attack
  • From: Chris <cmicel1@xxxxxxxxxxx>
• Re: Persistence memory attack
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Persistence memory attack
  • From: Chris <cmicel1@xxxxxxxxxxx>
• Help fixing crypt after using dmsetup remove_all
  • From: "James Whitt" <phikapjames@xxxxxxxxx>
• Re: cryptsetup is 100 times slower then in 1.0.6
  • From: Farkas Levente <lfarkas@xxxxxxxxxxx>
• Re: cryptsetup is 100 times slower then in 1.0.6
  • From: "Farkas Levente" <lfarkas@xxxxxxxxxxx>
• Re: cryptsetup: Problem with password-prompt when re-mapping encrypted partition
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: cryptsetup is 100 times slower then in 1.0.6
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: DM-Crypt missing in 2.6.24.7?
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: cryptsetup is 100 times slower then in 1.0.6
  • From: Lurkos <lurkos.usenet@xxxxxxxxx>
• DM-Crypt missing in 2.6.24.7?
  • From: Luke <sl@xxxxxxxxxxxxxxxxxx>
• Re: cryptsetup: Problem with password-prompt when re-mapping encrypted partition
  • From: Dominik Geyer <dominik.geyer@xxxxxx>
• cryptsetup is 100 times slower then in 1.0.6
  • From: Farkas Levente <lfarkas@xxxxxxxxxxx>
• cryptsetup is 100 times slower then in 1.0.6
  • From: Farkas Levente <lfarkas@xxxxxxxxxxx>
• Re: cryptsetup: Problem with password-prompt when re-mapping encrypted partition
  • From: Jonas <jonas@xxxxxxxxxxxxxxx>
• cryptsetup: Problem with password-prompt when re-mapping encrypted partition
  • From: Dominik Geyer <dominik.geyer@xxxxxx>
• temporarily forgetting a key
  • From: Adam Rosenstein <adam@xxxxxxxxxxxxx>
• Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Yan Li <elliot.li.tech@xxxxxxxxx>
• Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Yan Li <elliot.li.tech@xxxxxxxxx>
• Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: "Ritesh Raj Sarraf" <rrs@xxxxxxxxxxxxxx>
• Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Yan Li <elliot.li.tech@xxxxxxxxx>
• Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• [PATCH] remove duplicate sentence in manpage
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: Re: ?dm-crypt latency (seems to be solved)
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: ?dm-crypt latency (seems to be solved)
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: Re: Valid ciphers and modes for dmcrypt?
  • From: Lurkos <lurkos.usenet@xxxxxxxxx>
• Re: Re: Valid ciphers and modes for dmcrypt?
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Valid ciphers and modes for dmcrypt?
  • From: domiel <domiel42@xxxxxxxxxxxx>
• Re: Re: Valid ciphers and modes for dmcrypt?
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Valid ciphers and modes for dmcrypt?
  • From: domiel <domiel42@xxxxxxxxxxxx>
• Re: Valid ciphers and modes for dmcrypt?
  • From: domiel <domiel42@xxxxxxxxxxxx>
• Re: Valid ciphers and modes for dmcrypt?
  • From: domiel <domiel42@xxxxxxxxxxxx>
• Re: Valid ciphers and modes for dmcrypt?
  • From: Roscoe <eocsor@xxxxxxxxx>
• Valid ciphers and modes for dmcrypt?
  • From: domiel <domiel42@xxxxxxxxxxxx>
• A typo in homepage
  • From: "Lee, Dio" <Dio.Lee@xxxxxxxxxxxxxxxxx>
• Re: SSL weakness in openSSL
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Info about dm-crypt (without luksClose)
  • From: Pol Hallen <cryptsetup@xxxxxxxxxxxxxx>
• Re: Cryptsetup malfunctions??!!
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Cryptsetup malfunctions??!!
  • From: "Gilberto Nunes" <gilberto@xxxxxxxxxxxxx>
• Re: Hidden volumes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: fast CSPRNG?
  • From: Henrik Theiling <theiling@xxxxxxxxxx>
• Re: fast CSPRNG? [Was Re: Hidden volumes]
  • From: markus reichelt <ml@xxxxxxxxxxxxx>
• Re: Hidden volumes
  • From: markus reichelt <ml@xxxxxxxxxxxxx>
• Re: Hidden volumes
  • From: "Ma Begaj" <derliebegott@xxxxxxxxx>
• Re: Hidden volumes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Hidden volumes
  • From: "Ma Begaj" <derliebegott@xxxxxxxxx>
• Re: Hidden volumes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Hidden volumes
  • From: Lurkos <lurkos.usenet@xxxxxxxxx>
• fast CSPRNG? [Was Re: Hidden volumes]
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Hidden volumes
  • From: Arno Wagner <arno@xxxxxxxxxxx>
• Re: Hidden volumes
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Hidden volumes
  • From: Roscoe <eocsor@xxxxxxxxx>
• Hidden volumes
  • From: Lurkos <lurkos.usenet@xxxxxxxxx>
• Re: SSL weakness in openSSL
  • From: Roscoe <eocsor@xxxxxxxxx>
• SSL weakness in openSSL
  • From: Wolfgang Sailer <Wolfgang@xxxxxxxxxxxxxx>
• Read failed in read_blockwise
  • From: Thomas Mueller <thomas.mueller@xxxxxxx>
• FTP, pam_mount and LUKS
  • From: François Valenduc <francois.valenduc@xxxxxxxxxxxxx>
• segmentation fault with cryptsetup 1.0.6
  • From: "Oliver Metz" <oliver.metz@xxxxxx>
• Re: LUKS question
  • From: "Sanjay Sha" <sanjay.sha@xxxxxxxxx>
• Re: Can't access data anymore: has anything changed recently?
  • From: Joris <joris@xxxxx>
• Can't access data anymore: has anything changed recently?
  • From: Joris <joris@xxxxx>
• Re: /dev/random or urandom for encrypted swap
  • From: Nomen Nescio <nobody@xxxxxxxxx>
• Re: Re: /dev/random or urandom for encrypted swap
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: /dev/random or urandom for encrypted swap
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: /dev/random or urandom for encrypted swap
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• /dev/random or urandom for encrypted swap
  • From: Nomen Nescio <nobody@xxxxxxxxx>
• Re: Re: key chaining
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: key chaining
  • From: Michael Gebetsroither <gebi@xxxxxxxxxxxxxx>
• Re: key chaining
  • From: Roscoe <eocsor@xxxxxxxxx>
• key chaining
  • From: "Russ Dill" <russ.dill@xxxxxxxxx>
• Re: Re: ?dm-crypt latency
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• [2.6.25-rc8] dm crypt: fix ctx pending
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Chr <chunkeey@xxxxxx>
• Re: Re: ?dm-crypt latency
  • From: Mathieu SEGAUD <mathieu.segaud@xxxxxxxxx>
• Re: Re: ?dm-crypt latency
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: Re: ?dm-crypt latency
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Re: ?dm-crypt latency
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: 2.6.25-rc5-git6: Reported regressions from 2.6.24
  • From: Chr <chunkeey@xxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• Re: cryptsetup 1.0.3 and 1.0.5 incompatibilities
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• cryptsetup 1.0.3 and 1.0.5 incompatibilities
  • From: "Takuya Saitoh" <taka0038@xxxxxxxxx>
• cryptsetup -c anycipher-xts-plain:sha256 or not :sha256?
  • From: "Andreas Donig" <andreas.donig@xxxxxx>
• LUKS question
  • From: "Sanjay Sha" <sanjay.sha@xxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Ulrich Lukas <stellplatz-nr.13a@xxxxxxxxxxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Chr <chunkeey@xxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• Re: INFO: task mount:11202 blocked for more than 120 seconds
  • From: Chr <chunkeey@xxxxxx>
• INFO: task mount:11202 blocked for more than 120 seconds
  • From: Chr <chunkeey@xxxxxx>
• Re: Kernel 2.6.25-rc4: lock up when writing onto DM-Crypt volume
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Kernel 2.6.25-rc4: lock up when writing onto DM-Crypt volume
  • From: Ulrich Lukas <stellplatz-nr.13a@xxxxxxxxxxxxxxxxx>
• Re: Kernel 2.6.25-rc4: lock up when writing onto DM-Crypt volume
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Possibility of hash function besides SHA-1 in future LUKS revisions?
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: hex keys
  • From: dennis@xxxxxxxxxxxxxxxxx (Dennis Furey)
• Re: Kernel 2.6.25-rc4: lock up when writing onto DM-Crypt volume
  • From: Ulrich Lukas <stellplatz-nr.13a@xxxxxxxxxxxxxxxxx>
• Quick question about cryptsetup --align-payload
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: Possibility of hash function besides SHA-1 in future LUKS revisions?
  • From: Henrik Theiling <theiling@xxxxxxxxxx>
• Re: Kernel 2.6.25-rc4: lock up when writing onto DM-Crypt volume
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Kernel 2.6.25-rc4: lock up when writing onto DM-Crypt volume
  • From: Ulrich Lukas <stellplatz-nr.13a@xxxxxxxxxxxxxxxxx>
• Re: hex keys
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Re: md-raid5, dm-crypt, alignment and readahead
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: Re: md-raid5, dm-crypt, alignment and readahead
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
• Re: Cheaper encryption?
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: Cheaper encryption?
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Possibility of hash function besides SHA-1 in future LUKS revisions?
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: md-raid5, dm-crypt, alignment and readahead
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: hex keys
  • From: dennis@xxxxxxxxxxxxxxxxx (Dennis Furey)
• Re: Possibility of hash function besides SHA-1 in future LUKS revisions?
  • From: Henrik Theiling <theiling@xxxxxxxxxx>
• Re: cryptsetup 1.0.6 release
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• cryptsetup 1.0.6 release
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• md-raid5, dm-crypt, alignment and readahead
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: hex keys
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: hex keys
  • From: dennis@xxxxxxxxxxxxxxxxx (Dennis Furey)
• Re: resize
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: Possibility of hash function besides SHA-1 in future LUKS revisions?
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Possibility of hash function besides SHA-1 in future LUKS revisions?
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: resize
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Possibility of hash function besides SHA-1 in future LUKS revisions?
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: resize
  • From: Kévin REDON <kevredon@xxxxxxxxx>
• Re: resize
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: hex keys
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• hex keys
  • From: dennis@xxxxxxxxxxxxxxxxx (Dennis Furey)
• resize
  • From: Kévin REDON <kevredon@xxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: "Tony Luck" <tony.luck@xxxxxxxxx>
• Kernel 2.6.25-rc4: lock up when writing onto DM-Crypt volume
  • From: Ulrich Lukas <stellplatz-nr.13a@xxxxxxxxxxxxxxxxx>
• Re: [dm-devel] Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxxxxxx>
• Re: Re: resize and reload options to cryptsetup
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: compile warnings: differ in signedness & declared with attribute warn_unused_result
  • From: "Nikolay A. Fetisov" <naf@xxxxxxxxxxx>
• Re: cryptsetup-1.0.6-pre2
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• compile warnings: differ in signedness & declared with attribute warn_unused_result
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: Re: cryptsetup on arm *sometimes* gives "No key available" error
  • From: Carlo Wood <carlo@xxxxxxxxxx>
• Re: Re: cryptsetup on arm *sometimes* gives "No key available" error
  • From: JG <jg@xxxxxx>
• Re: Re: cryptsetup on arm *sometimes* gives "No key available" error
  • From: Carlo Wood <carlo@xxxxxxxxxx>
• Re: Re: cryptsetup on arm *sometimes* gives "No key available" error
  • From: JG <jg@xxxxxx>
• Re: cryptsetup on arm *sometimes* gives "No key available" error
  • From: Dick Middleton <gmane@xxxxxxxxxxxx>
• cryptsetup on arm *sometimes* gives "No key available" error
  • From: JG <jg@xxxxxx>
• Re: ?dm-crypt latency (seems to be solved)
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: cryptsetup-1.0.6-pre2
  • From: "Nikolay A. Fetisov" <naf@xxxxxxxxxxx>
• Re: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• cryptsetup-1.0.6-pre2
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: ?dm-crypt latency
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: [dm-devel] Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: [dm-devel] Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: ?dm-crypt latency
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: Re: ?dm-crypt latency
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Re: ?dm-crypt latency
  • From: Michael Hampton <error@xxxxxxxxxx>
• Re: ?dm-crypt latency
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: Re: ?dm-crypt latency
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: Re: ?dm-crypt latency
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Buffer overflow in wipeSpecial()
  • From: Henrik Theiling <theiling@xxxxxxxxxx>
• Re: ?dm-crypt latency
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: Who is using cryptsetup reload?
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Re: resize and reload options to cryptsetup
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Who is using cryptsetup reload?
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Buffer overflow in wipeSpecial()
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: aes-xts-benbi vs. aes-xts-plain
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: ?dm-crypt latency
  • From: Ulrich Lukas <stellplatz-nr.13a@xxxxxxxxxxxxxxxxx>
• Re: ?dm-crypt latency
  • From: Heinz Diehl <htd@xxxxxxxxxxxxxxxxx>
• ?dm-crypt latency
  • From: Gunter Ohrner <G.Ohrner@xxxxxxxxxxxxxxxxxxx>
• Re: aes-xts-benbi vs. aes-xts-plain
  • From: Ulrich Lukas <stellplatz-nr.13a@xxxxxxxxxxxxxxxxx>
• Re: Who is using cryptsetup reload?
  • From: Heinz Diehl <htd@xxxxxxxxxxxxxxxxx>
• Who is using cryptsetup reload?
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: aes-xts-benbi vs. aes-xts-plain
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• aes-xts-benbi vs. aes-xts-plain
  • From: Ulrich Lukas <stellplatz-nr.13a@xxxxxxxxxxxxxxxxx>
• Re: Buffer overflow in wipeSpecial()
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Buffer overflow in wipeSpecial()
  • From: ht@xxxxxxxxxxx (Henrik Theiling)
• Master key not erased?
  • From: ht@xxxxxxxxxxx (Henrik Theiling)
• Re: Re: Security against DRAM attacks
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Re: Security against DRAM attacks
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Re: Security against DRAM attacks
  • From: Bill Broadley <bill@xxxxxxxxxxxxxxx>
• Re: Re: Security against DRAM attacks
  • From: Bill Broadley <bill@xxxxxxxxxxxxxxx>
• Re: Re: Security against DRAM attacks
  • From: ht@xxxxxxxxxxx (Henrik Theiling)
• Re: Re: Security against DRAM attacks
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Security against DRAM attacks
  • From: Bill Broadley <bill@xxxxxxxxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: Michael Hampton <error@xxxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: noah <noah123@xxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: noah <noah123@xxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: Michael Gebetsroither <gebi@xxxxxxxxxxxxxx>
• Re: Cheaper encryption?
  • From: Jan Reusch <jreusch@xxxxxx>
• Re: Cheaper encryption?
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Security against DRAM attacks
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Security against DRAM attacks
  • From: Michael Hampton <error@xxxxxxxxxx>
• Security against DRAM attacks
  • From: Mikko Rauhala <mjrauhal@xxxxxxxxxxxxxx>
• Re: Scrub dm-crypt keys on reboot?
  • From: Michael Hampton <error@xxxxxxxxxx>
• Re: Cheaper encryption?
  • From: noah <noah123@xxxxxxxxx>
• Scrub dm-crypt keys on reboot?
  • From: noah <noah123@xxxxxxxxx>
• Re: Cheaper encryption?
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: "Michael S. Tsirkin" <m.s.tsirkin@xxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: Cheaper encryption?
  • From: Mathieu SEGAUD <mathieu.segaud@xxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Cheaper encryption?
  • From: morphium <morphium@xxxxxxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: Cheaper encryption?
  • From: Mathieu SEGAUD <mathieu.segaud@xxxxxxxxx>
• Re: Cheaper encryption?
  • From: morphium <morphium@xxxxxxxxxxxxx>
• Re: Cheaper encryption?
  • From: Grzegorz Kulewski <kangur@xxxxxxxxxx>
• Re: Cheaper encryption?
  • From: Andreas Westin <forsaken@xxxxxxxxxxx>
• Re: Cheaper encryption?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: cipher parameter in cryptsetup
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Cheaper encryption?
  • From: morphium <morphium@xxxxxxxxxxxxx>
• cipher parameter in cryptsetup
  • From: Evert <evert@xxxxxxxxxxxx>
• Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Re: Does dm-crypt actually work as a root device?
  • From: Evert Mouw <post@xxxxxxxxx>
• LUKS header at the end of partition?
  • From: icecutter@xxxxxxx
• Re: Does dm-crypt actually work as a root device?
  • From: Jason Haar <Jason.Haar@xxxxxxxxxxxxx>
• Re: Does dm-crypt actually work as a root device?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Does dm-crypt actually work as a root device?
  • From: Jason Haar <Jason.Haar@xxxxxxxxxxxxx>
• Re: LUKS partition gone?
  • From: "Sean Bushby" <sean.bushby@xxxxxxxxx>
• Re: LUKS partition gone?
  • From: icecutter@xxxxxxx
• Re: LUKS partition gone?
  • From: Carlo Wood <carlo@xxxxxxxxxx>
• LUKS partition gone?
  • From: "Sean Bushby" <sean.bushby@xxxxxxxxx>
• strange behaviour with cryptsetup
  • From: Heinz Diehl <htd@xxxxxxxxxxxxxxxxx>
• Re: Re: resize and reload options to cryptsetup
  • From: Uwe Menges <uwe.menges@xxxxxx>
• Snapshot of encrypted LV
  • From: Jens Müller <blog@xxxxxxxxxxxx>
• Re: LUKS header lost. Encryption key on USB thumbdrive
  • From: icecutter@xxxxxxx
• Re: LUKS header lost. Encryption key on USB thumbdrive
  • From: icecutter@xxxxxxx
• Re: LUKS header lost. Encryption key on USB thumbdrive
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: LUKS header lost. Encryption key on USB thumbdrive
  • From: "Lars G. Sander" <icecutter@xxxxxxx>
• Re: LUKS header lost. Encryption key on USB thumbdrive
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• LUKS header lost. Encryption key on USB thumbdrive
  • From: icecutter@xxxxxxx
• Re: Re: resize and reload options to cryptsetup
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: [patch 04/73] dm crypt: use bio_add_page
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Migration problem SuSE 10.0 -> dmcrypt
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• [PATCH] check keyIndex before actually using it as array index
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• Re: resize and reload options to cryptsetup
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Migration problem SuSE 10.0 -> dmcrypt
  • From: "Andreas K. Huettel" <A.K.Huettel@xxxxxxxxxx>
• cryptsetup luDelKey SEGFAULT
  • From: Nageswara R Sastry <nasastry@xxxxxxxxxx>
• [patch 03/73] dm crypt: fix write endio
  • From: Greg KH <gregkh@xxxxxxx>
• [patch 04/73] dm crypt: use bio_add_page
  • From: Greg KH <gregkh@xxxxxxx>
• resize and reload options to cryptsetup
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Is LUKS cluster save?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: data corruption with dmcrypt/LUKS
  • From: Dick Middleton <gmane@xxxxxxxxxxxx>
• Is LUKS cluster save?
  • From: Lars Täuber <lars.taeuber@xxxxxxx>
• Re: Re: data corruption with dmcrypt/LUKS
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: data corruption with dmcrypt/LUKS
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: data corruption with dmcrypt/LUKS
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: data corruption with dmcrypt/LUKS
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: data corruption with dmcrypt/LUKS
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• data corruption with dmcrypt/LUKS
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: [Pkg-cryptsetup-devel] Bug#460409: [dm-crypt] Re: [tobi@xxxxxxxxxxx: Bug#460409: cryptsetup: Cannot add Key to LUKS partition]
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Re: Multiple LUKS filesystems w/ 1 password
  • From: "Ma Begaj" <derliebegott@xxxxxxxxx>
• Re: Multiple LUKS filesystems w/ 1 password
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Multiple LUKS filesystems w/ 1 password
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [Pkg-cryptsetup-devel] Bug#460409: [dm-crypt] Re: [tobi@xxxxxxxxxxx: Bug#460409: cryptsetup: Cannot add Key to LUKS partition]
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: [Pkg-cryptsetup-devel] Bug#460409: [dm-crypt] Re: [tobi@xxxxxxxxxxx: Bug#460409: cryptsetup: Cannot add Key to LUKS partition]
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Encrypted Volume on SoftRaid5 got currupt at powerloss
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• Re: Encrypted Volume on SoftRaid5 got currupt at powerloss
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• Re: Encrypted Volume on SoftRaid5 got currupt at powerloss
  • From: Hans Huber <info@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Encrypted Volume on SoftRaid5 got currupt at powerloss
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: [Pkg-cryptsetup-devel] Bug#460409: [dm-crypt] Re: [tobi@xxxxxxxxxxx: Bug#460409: cryptsetup: Cannot add Key to LUKS partition]
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Re: [tobi@xxxxxxxxxxx: [Pkg-cryptsetup-devel] Bug#460409: cryptsetup: Cannot add Key to LUKS partition]
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Encrypted Volume on SoftRaid5 got currupt at powerloss
  • From: Hans Huber <info@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Encrypted Volume on SoftRaid5 got currupt at powerloss
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• Re: Re: [tobi@xxxxxxxxxxx: [Pkg-cryptsetup-devel] Bug#460409: cryptsetup: Cannot add Key to LUKS partition]
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: [tobi@xxxxxxxxxxx: [Pkg-cryptsetup-devel] Bug#460409: cryptsetup: Cannot add Key to LUKS partition]
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: problems to mount softraid5
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• [tobi@xxxxxxxxxxx: [Pkg-cryptsetup-devel] Bug#460409: cryptsetup: Cannot add Key to LUKS partition]
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Re: LUKS partitons disappeared
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: key size doesnt look right?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: key size doesnt look right?
  • From: oguh@xxxxxxx
• key size doesnt look right?
  • From: hellman <genix01@xxxxxxxxx>
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Uwe Menges <uwe.menges@xxxxxx>
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: wolfgang.aigner@xxxxxx
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: oguh@xxxxxxx
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: oguh@xxxxxxx
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Joris <joris@xxxxx>
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Uwe Menges <uwe.menges@xxxxxx>
• Re: problems to mount softraid5
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• Re: luks not working in 2.6.23.9 and up
  • From: Andreas Westin <forsaken@xxxxxxxxxxx>
• Re: Re: problems to mount softraid5
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: luks not working in 2.6.23.9 and up
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: problems to mount softraid5
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• luks not working in 2.6.23.9 and up
  • From: Andreas Westin <forsaken@xxxxxxxxxxx>
• Re: Re: problems to mount softraid5
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: LUKS partitons disappeared
  • From: "Robert Kelly" <bluethegrappler@xxxxxxxxx>
• SPAM: LOW * Re: problems to mount softraid5
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• Re: problems to mount softraid5
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• a luks format usb stick and the hal volume.label property
  • From: edA-qa mort-ora-y <info@xxxxxxxxxxxx>
• Re: Re: problems to mount softraid5
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: problems to mount softraid5
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• Intel's encryption in Eaglelake or should we trust hardware encryption?
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: problems to mount softraid5
  • From: Bruno Wolff III <bruno@xxxxxxxx>
• Re: problems to mount softraid5
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: problems to mount softraid5
  • From: Bruno Wolff III <bruno@xxxxxxxx>
• Re: problems to mount softraid5
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• problems to mount softraid5
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• Re: Probleme RAID 5 zu mounten
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Probleme RAID 5 zu mounten
  • From: Da Powah <dapowah@xxxxxxxxxxx>
• Re: LUKS partitons disappeared
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• LUKS partitons disappeared
  • From: "Robert Kelly" <bluethegrappler@xxxxxxxxx>
• Re: Proposal: cryptsetup 'tmp' with different filesystems
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: LUKS on dm-crypt: password stopped working
  • From: Ross Boylan <RossBoylan@xxxxxxxxxxxxxxxxxx>
• Re: LUKS on dm-crypt: password stopped working
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Proposal: cryptsetup 'tmp' with different filesystems
  • From: Hans-Peter Oeri <hp@xxxxxxx>
• LUKS on dm-crypt: password stopped working
  • From: Ross Boylan <RossBoylan@xxxxxxxxxxxxxxxxxx>
• [2.6.24 PATCH 06/06] dm crypt: use bio_add_page
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [2.6.24 PATCH 03/06] dm crypt: fix write endio
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• dm-crypt & LVM
  • From: "William Ottley" <williamottley@xxxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: someone <admin@xxxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: someone <admin@xxxxxxxxx>
• Re: Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: someone <admin@xxxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: someone <admin@xxxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: someone <admin@xxxxxxxxx>
• Re: Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: someone <admin@xxxxxxxxx>
• Re: Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: someone <admin@xxxxxxxxx>
• Re: Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: someone <admin@xxxxxxxxx>
• Re: Re: Re: Re: Re: Re: Re: cryptsetup luksOpen on USB-Disk
  • From: karsten gerber <karstengerber@xxxxxxxx>
• Re: FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• cryptsetup 1.0.6-pre1
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• cryptsetup: remove autogenerated files
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• [PATCH 3/3] cryptsetup: fix implicit function declarations
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• [PATCH 2/3] cryptsetup: logger function should return void
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• [PATCH 1/3] cryptsetup: the device parameter of LUKS_device_ready should be const
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• Re: LUKS unlocking with passphrase only in vitual console
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• LUKS unlocking with passphrase only in vitual console
  • From: Timo Scharwächter <manuke01@xxxxxx>
• Re: Re: Re: Re: Re: Re: cryptsetup luksOpen on USB-Disk
  • From: f-dm-c@xxxxxxxxxxxxx
• Re: Re: Re: Re: Re: Re: cryptsetup luksOpen on USB-Disk
  • From: karsten gerber <karstengerber@xxxxxxxx>
• Re: Re: Re: Re: Re: cryptsetup luksOpen on USB-Disk
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Re: Re: Re: Re: cryptsetup luksOpen on USB-Disk
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Re: Re: Re: cryptsetup luksOpen on USB-Disk
  • From: karsten gerber <karstengerber@xxxxxxxx>
• FW: Areca controller problem with Linux XFS over DM-CRYPT
  • From: "nickcheng" <nick.cheng@xxxxxxxxxxxx>
• Re: cryptsetup luksOpen on USB-Disk
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: Re: cryptsetup luksOpen on USB-Disk
  • From: karsten gerber <karstengerber@xxxxxxxx>
• Re: Keyfile Nameschema
  • From: "Stefan Gruber" <stef.gruber@xxxxxxxxx>
• Re: Keyfile Nameschema
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Keyfile Nameschema
  • From: "Stefan Gruber" <stef.gruber@xxxxxxxxx>
• Re: security implications in using sparse files?
  • From: Andreas <ahasenack@xxxxxxxxxxxx>
• Re: security implications in using sparse files?
  • From: Andreas <ahasenack@xxxxxxxxxxxx>
• Re: cryptsetup luksOpen on USB-Disk
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: security implications in using sparse files?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: cryptsetup luksOpen on USB-Disk
  • From: Lars Kruse <lists@xxxxxxxxxxxxx>
• Re: security implications in using sparse files?
  • From: Roscoe <eocsor@xxxxxxxxx>
• cryptsetup luksOpen on USB-Disk
  • From: karsten gerber <karstengerber@xxxxxxxx>
• security implications in using sparse files?
  • From: Andreas <ahasenack@xxxxxxxxxxxx>
• Check if device is allready crypted using cryptsetup
  • From: Stefan Agner <falstaff@xxxxxxxxxx>
• Re: NO corruptions in the dm-crypt layer 2.6.22
  • From: "Ma Begaj" <derliebegott@xxxxxxxxx>
• Re: NO corruptions in the dm-crypt layer 2.6.22
  • From: Joris <joris@xxxxx>
• Re: NO corruptions in the dm-crypt layer 2.6.22
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: NO corruptions in the dm-crypt layer 2.6.22
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: NO corruptions in the dm-crypt layer 2.6.22
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Corruptions in the dm-crypt layer 2.6.22
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: Corruptions in the dm-crypt layer 2.6.22
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Corruptions in the dm-crypt layer 2.6.22
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Corruptions in the dm-crypt layer 2.6.22
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Meaning of the --offset option in cryptsetup
  • From: octane indice <octane@xxxxxxxxxx>
• Re: Corruptions in the dm-crypt layer 2.6.22
  • From: "Dr. Ernst Molitor" <molitor@xxxxxxxxxxx>
• Re: Corruptions in the dm-crypt layer 2.6.22
  • From: "Ma Begaj" <derliebegott@xxxxxxxxx>
• Re: Corruptions in the dm-crypt layer 2.6.22
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Corruptions in the dm-crypt layer 2.6.22
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Corruptions in the dm-crypt layer 2.6.22
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: information about active mappings
  • From: "Janko Hrasko" <ojebat@xxxxxxxxx>
• Re: information about active mappings
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: information about active mappings
  • From: lars <lists@xxxxxxxxxxxxx>
• Re: information about active mappings
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• information about active mappings
  • From: "Janko Hrasko" <ojebat@xxxxxxxxx>
• Cannot open LUKS partition
  • From: "Leo Leo" <leo4mailing+dmcrypt@xxxxxxxxx>
• Re: Shell scripting and cryptsetup
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Shell scripting and cryptsetup
  • From: octane indice <octane@xxxxxxxxxx>
• Bug when using loopdevice?
  • From: "John Suijkerbuijk" <j.w.a.suijkerbuijk@xxxxxxxxx>
• Re: list of patches for cryptsetup 1.0.5
  • From: David Härdeman <david@xxxxxxxxxxx>
• Re: list of patches for cryptsetup 1.0.5
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: Re: list of patches for cryptsetup 1.0.5
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Re: Cryptsetup improvement
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Cryptsetup improvement
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• luksOpen takes long time
  • From: Jose Goncalves <jose.goncalves@xxxxxxx>
• Re: list of patches for cryptsetup 1.0.5
  • From: David Härdeman <david@xxxxxxxxxxx>
• Re: FreeOTFE.
  • From: Uwe Menges <uwe.menges@xxxxxx>
• Re: luksDelKey with current password
  • From: Andreas Hasenack <ahasenack@xxxxxxxxxxxx>
• Re: list of patches for cryptsetup 1.0.5 (gmame-dmcrypt: message 3 of 20)
  • From: Till Maas <opensource@xxxxxxxxx>
• FreeOTFE.
  • From: "Elad Shapira" <eladexposed@xxxxxxxxx>
• Re: Cryptsetup improvement
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• Re: Cryptsetup improvement
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• list of patches for cryptsetup 1.0.5
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Cryptsetup improvement
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Cryptsetup improvement
  • From: Giulio Genovese <giulio.genovese@xxxxxxxxxxxxx>
• Re: Key Revocation
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Key Revocation
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Key Revocation
  • From: "Gavin Wahl" <gavinwahl@xxxxxxxxx>
• Re: luksDelKey with current password
  • From: Roscoe <eocsor@xxxxxxxxx>
• luksDelKey with current password
  • From: Andreas Hasenack <ahasenack@xxxxxxxxxxxx>
• compiling cryptsetup without largefile support
  • From: Stephane Billiart <stephane.billiart@xxxxxxxxx>
• Re: Recommanded cipher settings
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Disagreement within the cryptsetup manual, cryptsetup 1.0.5
  • From: "Alexander Orlov" <alexander.orlov@xxxxxxxxx>
• Re: how to label encrypted partitions?
  • From: Harri <harald.dunkel@xxxxxxxxxxx>
• Re: how to label encrypted partitions?
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxxx>
• Re: Re: Recommanded cipher settings
  • From: Markus Schuster <ma.schuster@xxxxxx>
• Re: how to label encrypted partitions?
  • From: Dick Middleton <gmane@xxxxxxxxxxxx>
• Re: Re: how to label encrypted partitions?
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: how to label encrypted partitions?
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxxx>
• Re: Re: Recommanded cipher settings
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Recommanded cipher settings
  • From: Markus Schuster <ma.schuster@xxxxxx>
• Re: dm-crypt vs loop-aes
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: dm-crypt vs loop-aes
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: dm-crypt vs loop-aes
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Recommanded cipher settings
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Bad blocks and encrypted volume corruption
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Bad blocks and encrypted volume corruption
  • From: Eric St-Laurent <ericstl34@xxxxxxxxxxxx>
• Recommanded cipher settings
  • From: Eric St-Laurent <ericstl34@xxxxxxxxxxxx>
• dm-crypt vs loop-aes
  • From: Eric St-Laurent <ericstl34@xxxxxxxxxxxx>
• Re: how to label encrypted partitions?
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• how to label encrypted partitions?
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxxx>
• Re: Trouble with dm-crypt / luks and gpg protected key
  • From: Roscoe <eocsor@xxxxxxxxx>
• Trouble with dm-crypt / luks and gpg protected key
  • From: Christoffer Dahl Petersen <duca@xxxxxxxxxx>
• Re: Re: how to label encrypted partitions?
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: how to label encrypted partitions?
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: how to label encrypted partitions?
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxxx>
• Re: how to label encrypted partitions?
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• how to label encrypted partitions?
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxxx>
• Re: cryptsetup-luks and dietlibc
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: License for the specification of LUKS
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: [loficc-discuss] [dm-crypt] License for the specification of LUKS
  • From: Darren J Moffat <darrenm@xxxxxxxxxxxxxxx>
• Re: [loficc-discuss] [dm-crypt] License for the specification of LUKS
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: [loficc-discuss] [dm-crypt] License for the specification of LUKS
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• Re: [loficc-discuss] [dm-crypt] License for the specification of LUKS
  • From: Darren J Moffat <darrenm@xxxxxxxxxxxxxxx>
• Re: License for the specification of LUKS
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: License for the specification of LUKS
  • From: Clemens Fruhwirth <clemens@xxxxxxxxxxxxx>
• License for the specification of LUKS
  • From: Darren J Moffat <darrenm@xxxxxxxxxxxxxxx>
• Re: performance of dm-crypt devices?
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: performance of dm-crypt devices?
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: performance of dm-crypt devices?
  • From: Wolfgang Sailer <Wolfgang@xxxxxxxxxxxxxx>
• resource busy error
  • From: Trent Adams <trenta@xxxxxxxxxxxxx>
• Re: Fighting Keyloggers
  • From: "Klaus-J. Wolf" <yanestra@xxxxxxxxxx>
• Re: Fighting Keyloggers
  • From: "Ma Begaj" <derliebegott@xxxxxxxxx>
• Re: Fighting Keyloggers
  • From: "Klaus-J. Wolf" <yanestra@xxxxxxxxxx>
• Re: Fighting Keyloggers
  • From: Arno Wagner <wagner@xxxxxxxxxxxxxx>
• Re: Fighting Keyloggers
  • From: Roscoe <eocsor@xxxxxxxxx>
• Fighting Keyloggers
  • From: "Klaus-J. Wolf" <yanestra@xxxxxxxxxx>
• cryptsetup on avr32
  • From: W <wildan.m@xxxxxxxxx>
• performance of dm-crypt devices?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: change key
  • From: lars <lists@xxxxxxxxxxxxx>
• change key
  • From: Bruno Sampayo <bruno@xxxxxxxxxxxxxx>
• Re: "detect" ro devices automatically
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• "detect" ro devices automatically
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• bug in crypsetup-luks-1.0.5 __crypt_luks_open()
  • From: Jake Maciejewski <maciejej@xxxxxxxx>
• Re: Re: does dm-crypt have outstanding file corruption problems?
  • From: "Ma Begaj" <derliebegott@xxxxxxxxx>
• Re: Re: does dm-crypt have outstanding file corruption problems?
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: does dm-crypt have outstanding file corruption problems?
  • From: Jason Haar <Jason.Haar@xxxxxxxxxxxxx>
• Re: Re: Is my data destroyed? Mail containing errors etc.
  • From: Jan Reusch <jreusch@xxxxxx>
• Re: Is my data destroyed? Mail containing errors etc.
  • From: Dick Middleton <gmane@xxxxxxxxxxxx>
• Is my data destroyed? Mail containing errors etc.
  • From: Zambezi <zambezi@xxxxxxxxxxxxxxxx>
• Encryption and cluster filesystems
  • From: "Jochen Katz" <Diese.E-Mail-Adresse.ist.bereits.vergeben@xxxxxxxxxxxxxx>
• Benchmarking
  • From: Andrew Miklas <public@xxxxxxx>
• very slow dm-crypt write operation
  • From: Adriab <adriab@xxxxxxxxx>
• Re: luksFormat -- how long it takes?
  • From: Jan Reusch <jreusch@xxxxxx>
• luksFormat -- how long it takes?
  • From: Echo Choi <akoaoka@xxxxxxxxx>
• [patch] luksInit instead of luksFormat mentioned in libcryptsetup.h
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: Misleading Error Message - Partition Mounted before luksFormat
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Misleading Error Message - Partition Mounted before luksFormat
  • From: Sham Rao <sham@xxxxxxxx>
• Re: it *is* a luks partition, but cryptsetup says it isn't. corrupted header?
  • From: gambarimasu <gambarimasu+luks@xxxxxxxxx>
• Re: recovering a luks partition, when cryptsetup says it isnt one
  • From: Evgeni Golov <sargentd@xxxxxxxxxxxx>
• Re: [Bug 7388] Oops in kcryptd
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: recovering a luks partition, when cryptsetup says it isnt one
  • From: Roscoe <eocsor@xxxxxxxxx>
• recovering a luks partition, when cryptsetup says it isnt one
  • From: Evgeni Golov <sargentd@xxxxxxxxxxxx>
• Oops in kcryptd
  • From: "Laurent Parenteau" <laurent.parenteau@xxxxxxxxx>
• SPAM: LOW * Cryptsetup source won't compile on RHEL ES 4
  • From: Frans Maas <frans@xxxxxxxxxxxxxx>
• merits of cryptsetup without luks
  • From: gambarimasu <gambarimasu+luks@xxxxxxxxx>
• Re: split cryptsetup?
  • From: Till Maas <gmame-dmcrypt.20.boeh@xxxxxxxxxxxxxxx>
• Re: split cryptsetup?
  • From: Jan Reusch <jreusch@xxxxxx>
• Re: Luks on encrypted livecd's / Catalyst
  • From: Roscoe <eocsor@xxxxxxxxx>
• Re: Luks on encrypted livecd's / Catalyst
  • From: Raphaël Gertz <rapsys@xxxxxxx>
• Re: split cryptsetup?
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• split cryptsetup?
  • From: Thomas Zander <zander@xxxxxxx>
• Luks on encrypted livecd's / Catalyst
  • From: Nelson Batalha <nelson_batalha@xxxxxxx>
• Re: Patch to support LUKS UUIDs in libblkid
  • From: Karsten Hopp <karsten@xxxxxxxxxx>
• Re: Patch to support LUKS UUIDs in libblkid
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: does dm-crypt have outstanding file corruption problems?
  • From: Jason Haar <Jason.Haar@xxxxxxxxxxxxx>
• Re: does dm-crypt have outstanding file corruption problems?
  • From: Jason Haar <Jason.Haar@xxxxxxxxxxxxx>
• it *is* a luks partition, but cryptsetup says it isn't. corrupted header?
  • From: gambarimasu <gambarimasu+luks@xxxxxxxxx>
• Re: does dm-crypt have outstanding file corruption problems?
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• does dm-crypt have outstanding file corruption problems?
  • From: Jason Haar <Jason.Haar@xxxxxxxxxxxxx>
• Re: how to compile "cryptsetup-luks"? i get error :(
  • From: "Javier Chicano" <nycjv321@xxxxxxxxx>
• how to compile "cryptsetup-luks"? i get error :(
  • From: Javier Velasquez <nycjv321@xxxxxxxxx>
• Re: Patch to support LUKS UUIDs in libblkid
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: Failed to write to key storage
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: Failed to write to key storage
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: Re: Failed to write to key storage
  • From: Matthias Koenig <mkoenig@xxxxxxx>
• Re: Failed to write to key storage
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: Re: Failed to write to key storage
  • From: Carlo Wood <carlo@xxxxxxxxxx>
• Re: Re: Failed to write to key storage
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Failed to write to key storage
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: Re: Failed to write to key storage
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Re: Failed to write to key storage
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: Re: Failed to write to key storage
  • From: Carlo Wood <carlo@xxxxxxxxxx>
• Re: Failed to write to key storage
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: Re: Failed to write to key storage
  • From: Carlo Wood <carlo@xxxxxxxxxx>
• Re: Failed to write to key storage
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: Re: Failed to write to key storage
  • From: Carlo Wood <carlo@xxxxxxxxxx>
• Re: Failed to write to key storage
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Failed to write to key storage
  • From: Carlo Wood <carlo@xxxxxxxxxx>
• Re: cryptsetup luksOpen unreliable
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• LUKS and hashs
  • From: Markus <lists4me@xxxxxx>
• Re: Stack smashing detected durring cryptsetup luksOpen
  • From: Marcin Garski <mgarski@xxxxxxx>
• Re: Stack smashing detected durring cryptsetup luksOpen
  • From: Jonas Meurer <jonas@xxxxxxxxxxxxxxx>
• Stack smashing detected durring cryptsetup luksOpen
  • From: Marcin Garski <mgarski@xxxxxxx>
• cryptsetup luksOpen unreliable
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: LUKS partition is no longer recognized as such
  • From: Tobias Hunger <tobias.hunger@xxxxxxxxxxx>
• Massive speed problem with encrypted partition
  • From: Axel Gembe <ago@xxxxxxxxxxxxxx>
• Re: LUKS partition is no longer recognized as such
  • From: Sebastian Bork <bork@xxxxxxxxxxxxxxxx>
• LUKS partition is no longer recognized as such
  • From: Tobias Hunger <tobias.hunger@xxxxxxxxxxx>
• Re: dm-crypt and UUID instead of /dev/xxx
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: dm-crypt and UUID instead of /dev/xxx
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: Re: dm-crypt and UUID instead of /dev/xxx
  • From: rupert <rupertt@xxxxxxxxx>
• Re: dm-crypt and UUID instead of /dev/xxx
  • From: Dick Middleton <gmane@xxxxxxxxxxxx>