Re: [PATCH] fscrypt: Add support for AES-128-CBC
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: David Gstir <david@xxxxxxxxxxxxx>
- Subject: Re: [PATCH] fscrypt: Add support for AES-128-CBC
- From: Eric Biggers <ebiggers3@xxxxxxxxx>
- Date: Thu, 30 Mar 2017 23:36:01 -0700
- In-reply-to: <20170331062149.GA32409@zzz>
- References: <20170330173840.72909-1-david@sigma-star.at> <20170331062149.GA32409@zzz>
- User-agent: Mutt/1.8.0 (2017-02-23)
On Thu, Mar 30, 2017 at 11:21:49PM -0700, Eric Biggers wrote:
>
> Something else to consider (probably for the future; this doesn't necessarily
> have to be done yet) is that you really only need one essiv_tfm per *key*, not
> one per inode. To deduplicate them you'd need a hash table or LRU queue or
> something to keep track of the keys in use.
>
Sorry, I screwed this up. This wouldn't work because the ESSIV key is being
derived from the per-file key, not the master key.
- Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-fscrypt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[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]