Re: Btrfs Fscrypt Design Document
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Eric Biggers <ebiggers@xxxxxxxxxx>
- Subject: Re: Btrfs Fscrypt Design Document
- From: Vadim Akimov <lvd.mhm@xxxxxxxxx>
- Date: Tue, 26 Oct 2021 10:00:52 +0300
- In-reply-to: <YXcKX3iNmqlGsdzv@gmail.com>
- References: <YXGyq+buM79A1S0L@relinquished.localdomain> <YXcKX3iNmqlGsdzv@gmail.com>
On Mon, 25 Oct 2021 at 22:59, Eric Biggers <ebiggers@xxxxxxxxxx> wrote:
> However,
> given that btrfs is a copy-on-write filesystem and thus can support per-block
> metadata, a natural question is why not support an authenticated mode such as
> AES-GCM, with a nonce and authentication tag stored per block? Have you thought
> about this?
Can't the existing checksum fields be just reused to keep HMACs? This
way even the unencrypted metadata could be authenticated.
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[IETF Sipping]
[Info Cyrus]
[ALSA User]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite News]
[Deep Creek Hot Springs]
[Yosemite Campsites]
[ISDN Cause Codes]