@@ -6,17 +6,17 @@ your ownCloud. Encryption and decryption always happens server-side. This
6
6
enables the user to continue to use all the other apps to view and edit his
7
7
data.
8
8
9
- The app uses the users log-in password as encryption-password. This means that
10
- by default the user will loose access to his files if he looses his log-in
9
+ The app uses the user's log-in password as encryption-password. This means that
10
+ by default the user will lose access to his files if he loses his log-in
11
11
password.
12
12
13
13
It might be a good idea to make regular backups of all encryption keys. The
14
14
encryption keys are stored in following folders:
15
15
16
16
* data/owncloud_private_key (recovery key, if enabled and public share key)
17
17
* data/public-keys (public keys from all users)
18
- * data/<user>/files_encryption (users private key and all other keys necessary to
19
- decrypt the users files)
18
+ * data/<user>/files_encryption (users' private keys and all other keys necessary to
19
+ decrypt the users' files)
20
20
21
21
Enable File Recovery Feature
22
22
----------------------------
@@ -25,7 +25,7 @@ The admin can offer the user some kind of protection against password
25
25
loss. Therefore you have to enable the recovery key in the admin settings and
26
26
provide a strong recovery key password. The admin settings also enables you to
27
27
change the recovery key password if you wish. But you should make sure to never
28
- loose this password, because that's the only way to recover users files.
28
+ lose this password, because that's the only way to recover users' files.
29
29
30
30
Once the recovery key was enabled every user can choose in his personal
31
31
settings to enable this feature or not.
@@ -35,22 +35,22 @@ Recover User Files
35
35
36
36
If the recovery feature was enabled the admin will see a additional input field
37
37
at the top of the user management settings. After entering the recovery-key
38
- password the admin can change the users log-in password which will
39
- automatically recover the users file.
38
+ password the admin can change the user's log-in password which will
39
+ automatically recover the user's file.
40
40
41
41
If you use a user back-end which doesn't allow you to change the log-in
42
42
password directly within ownCloud, e.g. the LDAP back-end, than you can follow
43
- the same procedure to recover users files. The only difference is that
43
+ the same procedure to recover a user's files. The only difference is that
44
44
you need to change the log-in password additionally at your back-end. In this
45
45
case make sure to use both times the same password.
46
46
47
47
LDAP and other external user back-ends
48
48
--------------------------------------
49
49
50
- if you configure a external user back-end you will be able to change the users log-in password
51
- at the back-end. Since the encryption password must be the same as the users log-in password
50
+ if you configure a external user back-end you will be able to change the user's log-in password
51
+ at the back-end. Since the encryption password must be the same as the user's log-in password
52
52
this will result in a non-functional encryption system. If the recovery feature was enabled,
53
- the administrator will be able to recover the users files directly over the recovery feature.
53
+ the administrator will be able to recover the user's files directly over the recovery feature.
54
54
See the description above. Otherwise the user will be informed that his log-in password and
55
55
his encryption password no longer matchs after his next log-in. In this case the user will be
56
56
able to adjust his encryption password in the personal settings by providing both, his old and
0 commit comments