File corruption for ecryptfs files #24416
Comments
|
I also use ecryptfs locally, but I sync the mounted part that is non-encrypted. (I also have encryption enabled on the server) So you are syncing the encrypted ecryptfs files with scrambled file names. I suspect that this will not work correctly because it is likely that ecryptfs will use special characters that cannot be synced by ownCloud properly. Well, actually the sync client should refuse to sync such files. Maybe you discovered a set of special characters that aren't blocked but get mis-encoded in URLs or so, maybe even normalized by the server. I'd recommend using ecryptfs with non-scrambled file names instead. |
Interesting. I'm not sure if it's legal in my country to store personal details (e.g. documents about clients with their name (which is a personal detail) in the filename) unencrypted on a third party computer, so it would require a lot of work to anonymize filenames, and I would lose some convenience. But interesting. On the other hand, ecryptfs scrambled filenames are Also, permissions aren't stored in the filename, right? How do entries like this happen? |
|
@Redsandro actually all I said above is theory, was just guessing. If ecryptfs uses only ASCII chars for scrambling, then it should work. Looking at your post above, it looks like even the file names get corrupted ? Or was it the file contents ? |
|
@PVince81 Yes, especially the filenames. I actually cannot verify in all certainty if the contents got corrupted, because I cannot open the files anymore. |
|
It almost looks like your FS itself got corrupted somehow. I don't see any way your file names could get corrupted that way by ownCloud. |
|
Are you still seeing this issue with OC 9.0.4 ? |
|
9.0.4? I'm pretty far from that, and it claims to be the latest version.
|
|
you're looking at the client version. 9.0.4 is the server version |
|
Oh I wouldn't know. Is there a way to figure this out without having control over the server?
|
|
@Redsandro yes, log in on the server with the web UI, then go to the personal page. |
|
I guess I'm out of luck. The server (out of my control, controlled by stackstorage.com) is: If you have a commit pointing to a file corruption fix, maybe I can convince them it's important enough to upgrade hundreds of servers. |
|
8.2 will be EOL in June 2017. That should also be a reason to update. |
|
Problem might be related to long file names: #25425 |
|
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to reproduce
Expected behaviour
No problems
Actual behaviour
Corrupted files. Trying to
chmodrecursively shows problems like this. I think less than 1% of my files is affected:Trying to
lsin one of the dirs with problems:Server configuration
Not sure, using Stack from TransIP - stackstorage.com
Client configuration
Operating system: Ubuntu 14.04 LTS
ownCloud version:
2.1.1deb http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_14.04/ /Logs
ownCloud log (data/owncloud.log)
There is this a hundred times. Not sure if it's relevant.
All other lines are like this:
I'm not sure if this is OwnCloud or ecryptfs related, so I posted an ecryptfs related bug here: https://bugs.launchpad.net/ecryptfs/+bug/1577740
However, I did not notice any of this before I switched from Dropbox to OwnCloud. Either that points to OwnCloud, or it's just a coincidence.
The text was updated successfully, but these errors were encountered: