summaryrefslogtreecommitdiffstats
path: root/apps/files/appinfo/version
diff options
context:
space:
mode:
authorJoas Schilling <nickvergessen@owncloud.com>2015-07-23 18:27:05 +0200
committerJoas Schilling <nickvergessen@owncloud.com>2015-07-24 10:37:39 +0200
commit20cf8ec205fb796ec919071f193b7f6f1ab2ae76 (patch)
tree60a708e43dc54fb3a29eccf032774167bddf2e93 /apps/files/appinfo/version
parent42baeb36dce9999f91763ef9d24103b4c52ff03b (diff)
downloadnextcloud-server-20cf8ec205fb796ec919071f193b7f6f1ab2ae76.tar.gz
nextcloud-server-20cf8ec205fb796ec919071f193b7f6f1ab2ae76.zip
Add an update script to reset the value
In case encryption was not enabled, we accidently set encrypted = 1 for files inside mount points, since 8.1.0. This breaks opening the files in 8.1.1 because we fixed the code that checks if a file is encrypted. In order to fix the file, we need to reset the flag of the file. However, the flag might be set because the file is in fact encrypted because it was uploaded at a time where encryption was enabled. So we can only do this when: - Current version of ownCloud before the update is 8.1.0 or 8.2.0.(0-2) - Encryption is disabled - files_encryption is not known in the app config If the first two are not the case, we are save. However, if files_encryption values exist in the config, we might have a false negative here. Now if there is no file with unencrypted size greater 0, that means there are no files that are still encrypted with "files_encryption" encryption. So we can also safely reset the flag here. If this is not the case, we go with "better save then sorry" and don't change the flag but write a message to the ownCloud log file.
Diffstat (limited to 'apps/files/appinfo/version')
-rw-r--r--apps/files/appinfo/version2
1 files changed, 1 insertions, 1 deletions
diff --git a/apps/files/appinfo/version b/apps/files/appinfo/version
index 512a1faa680..5ed5faa5f16 100644
--- a/apps/files/appinfo/version
+++ b/apps/files/appinfo/version
@@ -1 +1 @@
-1.1.9
+1.1.10