gmane.linux.kernel.device-mapper.dm-crypt archive
718 archived articles, newest first (page 5 of 8). Latest articles →
[PATCH v2] dm crypt: add flags to optionally bypass dm-crypt workqueues
Fri, 26 Jun 2020 22:03:02 +0100DM-integrity questions, a storage-stack plan with request for critique/feedback
Fri, 26 Jun 2020 10:51:10 -0400Re: [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Wed, 24 Jun 2020 18:00:45 +0100Re: [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Wed, 24 Jun 2020 09:24:07 -0700Re: [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Wed, 24 Jun 2020 09:24:07 +0100Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Wed, 24 Jun 2020 09:02:39 +0100Re: [dm-devel] [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Wed, 24 Jun 2020 07:49:38 +0000Re: [dm-devel] [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Wed, 24 Jun 2020 07:24:46 +0000Re: [dm-devel] [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Wed, 24 Jun 2020 06:46:33 +0000Re: [dm-devel] [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Tue, 23 Jun 2020 22:27:39 -0700Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Wed, 24 Jun 2020 01:22:09 -0400Re: [dm-devel] [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Wed, 24 Jun 2020 05:21:24 +0000Re: [dm-devel] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Wed, 24 Jun 2020 05:12:40 +0000Re: [dm-crypt] [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Tue, 23 Jun 2020 22:04:52 -0700Re: [dm-devel] [RFC PATCH 0/1] dm-crypt excessive overhead
Wed, 24 Jun 2020 04:54:18 +0000Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Wed, 24 Jun 2020 04:28:14 +0000Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Wed, 24 Jun 2020 10:23:01 +1000Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Tue, 23 Jun 2020 17:24:39 +0100Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Tue, 23 Jun 2020 11:33:52 -0400Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Tue, 23 Jun 2020 11:22:36 -0400Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Tue, 23 Jun 2020 16:07:33 +0100Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Tue, 23 Jun 2020 11:01:18 -0400Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Mon, 22 Jun 2020 08:08:47 +0000Re: [dm-devel] [RFC PATCH 0/1] dm-crypt excessive overhead
Mon, 22 Jun 2020 08:55:05 +0100Re: How many errors can be corrected by FEC? ( DM-verity)
Mon, 22 Jun 2020 09:42:20 +0200Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Mon, 22 Jun 2020 09:33:40 +0200How many errors can be corrected by FEC? ( DM-verity)
Mon, 22 Jun 2020 11:40:54 +0530Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Mon, 22 Jun 2020 00:45:19 +0000Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Sun, 21 Jun 2020 13:20:21 -0700Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Sun, 21 Jun 2020 01:53:26 +0200Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Sat, 20 Jun 2020 22:02:36 +0100Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Sat, 20 Jun 2020 15:36:21 -0400 (EDT)Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Sat, 20 Jun 2020 17:26:32 +0000 (UTC)Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Sat, 20 Jun 2020 11:46:02 +0200Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Sat, 20 Jun 2020 11:07:32 +0200Re: FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Sat, 20 Jun 2020 08:10:31 +0200Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Sat, 20 Jun 2020 11:23:33 +1000FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Fri, 19 Jun 2020 22:45:51 +0200Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Fri, 19 Jun 2020 20:44:58 +0100Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Fri, 19 Jun 2020 14:39:39 -0400 (EDT)Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Fri, 19 Jun 2020 12:55:49 -0400FEC: Error correction happens only on the verity devive
Fri, 19 Jun 2020 10:16:06 +0530[RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target
Fri, 19 Jun 2020 17:41:32 +0100[RFC PATCH 0/1] dm-crypt excessive overhead
Fri, 19 Jun 2020 17:41:31 +0100Re: bug in cryptsetup --header option when using luksFormat?
Mon, 15 Jun 2020 23:03:54 +0200Re: bug in cryptsetup --header option when using luksFormat?
Mon, 15 Jun 2020 17:33:49 +0200bug in cryptsetup --header option when using luksFormat?
Sun, 14 Jun 2020 19:03:07 +0200Re: can`t build "cryptsetup" release :-(
Sun, 14 Jun 2020 12:06:10 +0200can`t build "cryptsetup" release :-(
Fri, 12 Jun 2020 00:09:31 +0000Clarifications 2 to URGENT Help needed w LUKS on KDE Neon
Thu, 11 Jun 2020 20:24:59 +0000Update-Clarifications to URGENT Help needed w LUKS on KDE Neon
Wed, 10 Jun 2020 04:43:50 +0000URGENT Help needed w LUKS on KDE Neon
Mon, 08 Jun 2020 15:04:00 +0000Re: Understanding of --integrity* parameters for LUKS-independent dm-integrity setup
Sun, 31 May 2020 13:18:06 +0200[ANNOUNCE] cryptsetup 2.3.3
Thu, 28 May 2020 11:57:30 +0200Understanding of --integrity* parameters for LUKS-independent dm-integrity setup
Sun, 24 May 2020 21:45:56 +1000Re: FAQ :WAS: LUKS2 on disk format
Tue, 12 May 2020 16:28:27 +0200Re: LUKS2 on disk format
Tue, 12 May 2020 13:03:20 +0200LUKS2 on disk format
Tue, 12 May 2020 10:31:22 +0000Re: LUKS2 on disk format
Tue, 12 May 2020 11:54:51 +0200LUKS2 on disk format
Tue, 12 May 2020 05:48:14 +0000FAQ :WAS: LUKS2 on disk format
Mon, 11 May 2020 16:15:27 -0700Re: LUKS2 on disk format
Mon, 11 May 2020 21:58:09 +0200LUKS2 on disk format
Mon, 11 May 2020 19:07:35 +0000luks2 and discard/trim not working
Fri, 8 May 2020 23:41:34 +0200Re: luks2 and discard/trim not working
Sat, 9 May 2020 19:41:09 -0600Re: luks2 and discard/trim not working
Sun, 10 May 2020 00:01:06 +0200Re: luks2 and discard/trim not working
Sat, 9 May 2020 23:35:37 +0200Re: luks2 and discard/trim not working
Sat, 9 May 2020 14:23:01 -0600Re: luks2 and discard/trim not working
Sat, 9 May 2020 22:11:56 +0200Re: luks2 and discard/trim not working
Sat, 9 May 2020 21:41:59 +0200Re: luks2 and discard/trim not working
Sat, 9 May 2020 09:45:13 -0600luks2 and discard/trim not working
Sat, 9 May 2020 16:25:35 +0200Re: Restored luks2 header to wrong drive!
Tue, 5 May 2020 12:50:16 -0400Re: Restored luks2 header to wrong drive!
Tue, 5 May 2020 10:29:43 -0600Re: Restored luks2 header to wrong drive!
Tue, 5 May 2020 16:33:48 +0200Re: Restored luks2 header to wrong drive!
Tue, 5 May 2020 16:00:44 +0200Re: Restored luks2 header to wrong drive!
Tue, 5 May 2020 15:57:29 +0200Re: Restored luks2 header to wrong drive!
Tue, 5 May 2020 08:51:33 -0500Re: Restored luks2 header to wrong drive!
Tue, 5 May 2020 09:39:07 -0400Re: Restored luks2 header to wrong drive!
Tue, 5 May 2020 09:20:47 +0000Restored luks2 header to wrong drive!
Mon, 4 May 2020 23:07:24 -0400Re: cryptsetup gui
Sun, 3 May 2020 00:57:58 +0200 (CEST)Re: cryptsetup gui
Fri, 1 May 2020 22:59:44 +0200Re: cryptsetup gui
Fri, 1 May 2020 16:08:28 +0000cryptsetup gui
Fri, 1 May 2020 15:44:06 +0200 (CEST)[ANNOUNCE] cryptsetup 2.3.2
Thu, 30 Apr 2020 17:20:44 +0200Re: FAQ rework for LUKS2: First pass done
Tue, 28 Apr 2020 15:30:22 +0200Re: Some Q&A about LUKS2 reencryption
Mon, 27 Apr 2020 19:05:22 +0200Re: Some Q&A about LUKS2 reencryption
Mon, 27 Apr 2020 17:27:28 +0200Re: FAQ rework for LUKS2: First pass done
Mon, 27 Apr 2020 14:37:22 +0000 (UTC)Re: Some Q&A about LUKS2 reencryption
Mon, 27 Apr 2020 16:25:09 +0200Some Q&A about LUKS2 reencryption
Mon, 27 Apr 2020 10:39:05 +0200FAQ rework for LUKS2: First pass done
Sun, 26 Apr 2020 18:31:51 +0200Adding a drive, and OS
Fri, 24 Apr 2020 16:33:34 -0700Re: SVG of LUKS icon
Wed, 22 Apr 2020 19:04:15 +0200Re: SVG of LUKS icon
Tue, 21 Apr 2020 14:23:05 -0700Re: SVG of LUKS icon
Tue, 21 Apr 2020 19:10:26 +0200SVG of LUKS icon
Tue, 21 Apr 2020 02:55:52 +0000Re: cryptsetup Yubikey challenge-response support
Thu, 16 Apr 2020 12:36:07 +0200Re: cryptsetup Yubikey challenge-response support
Wed, 15 Apr 2020 19:03:19 -0700
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.