New file could not be encrypted due to an error from the Qualcomm crypto module in OpenWRT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Steps to encryt the file in openwrt
Created new directory --> mkdir tests
root@OpenWrt:/# mount.ecryptfs tests/ tests/
Unable to find a list of options to parse, defaulting to interactive mount
Passphrase:
Select cipher:
1) aes: blocksize = 16; min keysize = 16; max keysize = 32
2) blowfish: blocksize = 8; min keysize = 16; max keysize = 56
3) des3_ede: blocksize = 8; min keysize = 24; max keysize = 24
4) twofish: blocksize = 16; min keysize = 16; max keysize = 32
5) cast6: blocksize = 16; min keysize = 16; max keysize = 32
6) cast5: blocksize = 8; min keysize = 5; max keysize = 16
aes
Selection [aes]: Select key bytes:
1) 16
2) 32
3) 24
32
n
n
Unable to find a list of options to parse, defaulting to interactive mount
Selection [16]: Enable plaintext passthrough (y/n) [n]: Enable filename encryption (y/n) [n]: Attempting to mount w:
ecryptfs_
ecryptfs_
ecryptfs_
ecryptfs_
Mounted eCryptfs
Copied the random file to encrypt
root@OpenWrt:/# cp /etc/hosts tests/
[ 2947.608917] crypt_extent: Error attempting to crypt page with page_index = [0], extent_offset = [0]; rc = [-22]
[ 2947.608951] ecryptfs_
[ 2947.629065] ecryptfs_write_end: Error encrypting page (upper index [0x000000000000
[ 2947.629163] crypt_extent: Error attempting to crypt page with page_index = [0], extent_offset = [0]; rc = [-22]
[ 2947.636273] ecryptfs_
[ 2947.659065] ecryptfs_write_end: Error encrypting page (upper index [0x000000000000
cp: write error: Invalid argument
Why I have this error, does anyone have any idea ?
tags: | added: ecryptfs |
tags: | added: ecryptfs-utils |
Changed in ecryptfs: | |
status: | New → Incomplete |
summary: |
- File is not encrypted after mounting + New file could not be encrypted due to an error from the Qualcomm crypto + module in OpenWRT |
Changed in ecryptfs: | |
status: | Won't Fix → Invalid |
Hey Raj - I have a few questions:
1) What kernel and architecture is this? (uname -a)
2) Can you attach the contents of /proc/crypto after reproducing this issue?
3) Can you attach the contents of /proc/keys after reproducing this issue?
Thanks!