FS#50442 - [ecryptfs-utils] 108-2: Not decrypting non-FNEK files on FNEK-enabled FS
Attached to Project:
Community Packages
Opened by Aaron Moore (usagi) - Friday, 19 August 2016, 00:53 GMT
Last edited by Balló György (City-busz) - Saturday, 27 January 2018, 02:17 GMT
Opened by Aaron Moore (usagi) - Friday, 19 August 2016, 00:53 GMT
Last edited by Balló György (City-busz) - Saturday, 27 January 2018, 02:17 GMT
|
Details
Description:
I had a share that contained files in an ecryptfs system. These files were initially made without an FNEK. I eventually switched to using an FNEK and new files were created using this key, but the old files are still non-FNEK encrypted. This has worked for years. After an update yesterday (which did NOT include an update to this package), the files that are non-filename-encrypted are shown as broken inodes. If i re-mount without an FNEK, the files are accessible. I feel that this might be a conflict between some dependancy and this package, and i intend to attempt to track it down. Additional info: * package version(s) 108-2 * config and/or log files etc. Steps to reproduce: :Create files an an ecryptfs with no FNEK :Remount with FNEK :Files will not be available. |
This task depends upon
Closed by Balló György (City-busz)
Saturday, 27 January 2018, 02:17 GMT
Reason for closing: No response
Saturday, 27 January 2018, 02:17 GMT
Reason for closing: No response
Comment by
Timothy Redaelli (tredaelli) -
Monday, 12 December 2016, 16:54 GMT
Can you re-test this using ecryptfs-utils 111?