DM-Crypt Archive mirror
 help / color / mirror / Atom feed
From: David Niklas <doark@mail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Streaming ciphers
Date: Sat, 15 Feb 2020 19:59:41 -0500	[thread overview]
Message-ID: <20200215195941.7ef400b3@Phenom-II-x6.niklas.com> (raw)

Hello,
Today I was helping a poor luser who's Crucial P1 QLC SSD died from
too many writes. We still don't know what's doing the writing, but he is
running luks using FDE so write amplification is definitely a
factor.
I forget the answer to this so please enlighten me, is there a streaming
cypher he can use instead of a block cipher? A better option that I
didn't consider?
Not that the TCG Opal is to be fully trusted (nor is it available on
that model), but how does it work with respect to write amplification vs.
luks?

Thanks,
David

             reply	other threads:[~2020-02-16  1:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16  0:59 David Niklas [this message]
2020-02-16  2:32 ` [dm-crypt] Streaming ciphers Arno Wagner
2020-02-16 13:58   ` Matthias Schniedermeyer
2020-02-17  3:56     ` David Niklas
2020-02-17 10:49       ` Matthias Schniedermeyer

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=20200215195941.7ef400b3@Phenom-II-x6.niklas.com \
    --to=doark@mail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).