~hc/RK356X_SDK_RELEASE.git

..	..	@@ -5,10 +5,10 @@
5	5	ECryptfs is a stacked filesystem which transparently encrypts and decrypts each
6	6	file using a randomly generated File Encryption Key (FEK).
7	7
8		-Each FEK is in turn encrypted with a File Encryption Key Encryption Key (FEFEK)
	8	+Each FEK is in turn encrypted with a File Encryption Key Encryption Key (FEKEK)
9	9	either in kernel space or in user space with a daemon called 'ecryptfsd'. In
10	10	the former case the operation is performed directly by the kernel CryptoAPI
11		-using a key, the FEFEK, derived from a user prompted passphrase; in the latter
	11	+using a key, the FEKEK, derived from a user prompted passphrase; in the latter
12	12	the FEK is encrypted by 'ecryptfsd' with the help of external libraries in order
13	13	to support other mechanisms like public key cryptography, PKCS#11 and TPM based
14	14	operations.
..	..	@@ -22,12 +22,12 @@
22	22	The 'encrypted' key type has been extended with the introduction of the new
23	23	format 'ecryptfs' in order to be used in conjunction with the eCryptfs
24	24	filesystem. Encrypted keys of the newly introduced format store an
25		-authentication token in its payload with a FEFEK randomly generated by the
	25	+authentication token in its payload with a FEKEK randomly generated by the
26	26	kernel and protected by the parent master key.
27	27
28	28	In order to avoid known-plaintext attacks, the datablob obtained through
29	29	commands 'keyctl print' or 'keyctl pipe' does not contain the overall
30		-authentication token, which content is well known, but only the FEFEK in
	30	+authentication token, which content is well known, but only the FEKEK in
31	31	encrypted form.
32	32
33	33	The eCryptfs filesystem may really benefit from using encrypted keys in that the