From: Josef Bacik <josef@redhat.com>
To: Jay Sullivan <notfed@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Encryption in btrfs
Date: Tue, 18 May 2010 15:03:59 -0400 [thread overview]
Message-ID: <20100518190358.GA3108@localhost.localdomain> (raw)
In-Reply-To: <AANLkTilBRFysT-FvWjYqGUQIzWZf8HEmBQz9P0Ck9kNm@mail.gmail.com>
On Tue, May 18, 2010 at 02:54:35PM -0400, Jay Sullivan wrote:
> Hi,
>=20
> In the past, I've heard rumors that there are plans to support
> [transparent] encryption in btrfs. =A0If you guys were able to get
> compression to work already, I don't see what's stopping you from
> implementing encryption. =A0I'd like to strongly recommend that you l=
ook
> into using=A0the "NaCl: Networking and Cryptography library" (see
> http://nacl.cace-project.eu/ =A0) by Daniel J. Bernstein. It is
> extremely lightweight, fast, secure, and has an extremely simple API.
> I'd really like to see btrfs take advantage of such a great
> cryptographic library. I'm interested in hearing all of your thought=
s
> on this, as I think it could work out quite nicely.
>=20
Whenever somebody manages to get around to encryption it will likely us=
e the
built in crypto library already in the kernel so we don't go around dup=
licating
code. Thanks,
Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-18 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 18:54 Encryption in btrfs Jay Sullivan
2010-05-18 19:03 ` Josef Bacik [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-26 22:51 Kirill A. Shutemov
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=20100518190358.GA3108@localhost.localdomain \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=notfed@gmail.com \
/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.