From: Vladimir Ivanovich <aj63g5u0@cocaine.ninja>
To: cryptsetup@lists.linux.dev
Subject: luks ssd idea
Date: Mon, 22 Sep 2025 19:29:18 +0200 [thread overview]
Message-ID: <20250922192919.4d4b3992@desktop> (raw)
hello
luks default is disable ssd trim-discard command because leaks unused
blocks
what if shuffle data, maybe another mapper device, to leak less info?
fpe(n, key, i) = format preserving encryption, domain {0...n}
roll(n, offset, i) = (i + offset) % n
block_out = fpe(DISK_SIZE / BLOCK_SIZE, hkdf(LUKS_SHUFFLEBLOCK,
masterkey), block_in) page_out = roll(BLOCK_SIZE / PAGE_SIZE,
hash(hkdf(LUKS_SHUFFLEINDEX, masterkey) + block_in) % (BLOCK_SIZE /
PAGE_SIZE), page_in)
sorry for bad english, what you guys think of my proposal
reply other threads:[~2025-09-22 17:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250922192919.4d4b3992@desktop \
--to=aj63g5u0@cocaine.ninja \
--cc=cryptsetup@lists.linux.dev \
/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