From: Alexander Koch <mail@alexanderkoch.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.4.0
Date: Thu, 27 Oct 2011 15:33:31 +0200 [thread overview]
Message-ID: <4EA95DAB.5020402@alexanderkoch.net> (raw)
In-Reply-To: <4EA85582.3080904@redhat.com>
Am 26.10.2011 20:46, schrieb Milan Broz:
> * Support --enable-discards option to allow discards/TRIM requests.
>
> Since kernel 3.1, dm-crypt devices optionally (not by default) support
> block discards (TRIM) comands.
> If you want to enable this operation, you have to enable it manually
> on every activation using --enable-discards
>
> cryptsetup luksOpen --enable-discards /dev/sdb test_disk
>
> WARNING: There are several security consequences, please read at least
> http://asalor.blogspot.com/2011/08/trim-dm-crypt-problems.html
> before you enable it.
On Arch Linux, the package 'cryptsetup' contains
/lib/initcpio/hooks/encrypt, which provides a hook for mounting
encrypted volumes from initrd.
Does anyone know if there exists any effort on making this script accept
options for cryptsetup from kernel cmdline?
The current version only reads device and mapper-name, so one cannot
open an encrypted root device with discard enabled.
Looking at the code, I think this would not be so hard to implement
(maybe just an addidional ':'-separated field in the kernel cmdline for
options like --enable-discards), but If someone is already working on it
I won't start the hack ;)
Cheers,
lynix
next prev parent reply other threads:[~2011-10-27 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 18:46 [dm-crypt] [ANNOUNCE] cryptsetup 1.4.0 Milan Broz
2011-10-27 13:33 ` Alexander Koch [this message]
2011-10-27 14:27 ` Christian Hesse
2011-10-28 13:49 ` Heinz Diehl
2011-11-09 12:46 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.4.1 Milan Broz
2012-04-12 8:38 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.4.2 Milan Broz
2012-05-31 8:38 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.4.3 Milan Broz
2012-05-31 9:26 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA95DAB.5020402@alexanderkoch.net \
--to=mail@alexanderkoch.net \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox