From: Andrei Bacs <andrei.bacs@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: cpu808694@gmail.com, Cristiano Giuffrida <c.giuffrida@vu.nl>,
"Bos, H.J." <h.j.bos@vu.nl>, Kaveh Razavi <kaveh@ethz.ch>,
"Bacs, A." <a.bacs@vu.nl>
Subject: inline deduplication security issues
Date: Sat, 22 Jan 2022 19:42:47 +0100 [thread overview]
Message-ID: <CAKDzk=-HZardsLFH5c9HYre73NYNszUJqpfsh0YJnnaQToB3BA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
Hi,
We have found security issues with inline deduplication in storage
systems, using ZFS and Btrfs and running examples. See the attached
paper for details.
The paper will be presented at FAST'22 and thus our findings will be
public by 23rd of February 2022.
Please let us know if you plan to deploy any defenses (such as the one
we describe in the paper) by 23rd of February 2022. If not, we can
make our findings public earlier.
Andrei
[-- Attachment #2: paper.pdf --]
[-- Type: application/pdf, Size: 269987 bytes --]
next reply other threads:[~2022-01-22 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 18:42 Andrei Bacs [this message]
2022-01-23 19:18 ` inline deduplication security issues Diego Calleja
2022-01-24 1:38 ` Su Yue
2022-01-24 11:45 ` Qu Wenruo
2022-01-24 16:17 ` David Sterba
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='CAKDzk=-HZardsLFH5c9HYre73NYNszUJqpfsh0YJnnaQToB3BA@mail.gmail.com' \
--to=andrei.bacs@gmail.com \
--cc=a.bacs@vu.nl \
--cc=c.giuffrida@vu.nl \
--cc=cpu808694@gmail.com \
--cc=h.j.bos@vu.nl \
--cc=kaveh@ethz.ch \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.