Make the KeyStore warning a bit clearer
This commit is contained in:
parent
fe49ec93ee
commit
ae71f8e48d
1 changed files with 3 additions and 3 deletions
|
@ -14,9 +14,9 @@
|
||||||
device supports it). However, as the keys are not stored with the apps data, <b>this method
|
device supports it). However, as the keys are not stored with the apps data, <b>this method
|
||||||
prevents external backup solutions (like Titanium) from working</b>. If you choose this
|
prevents external backup solutions (like Titanium) from working</b>. If you choose this
|
||||||
method you will have to rely on the internal backup functions provided by <b>andOTP</b>.
|
method you will have to rely on the internal backup functions provided by <b>andOTP</b>.
|
||||||
\n\n<b>Warning</b>: The KeyStore is known to cause problems on some custom ROMs (and a few
|
\n\n<b>Warning</b>: The KeyStore is known to cause a lot of problems, please only use it if
|
||||||
stock ones as well). If you don\'t mind entering a password / PIN every time you start
|
you absolutely have to. If you don\'t mind entering a password / PIN every time you start
|
||||||
<b>andOTP</b> it is highly recommended to use the password-based encryption instead.</string>
|
<b>andOTP</b> it is <b>highly recommended to use the password-based encryption instead</b>.</string>
|
||||||
<string name="intro_slide2_desc_password">This method will encrypt your data with a key
|
<string name="intro_slide2_desc_password">This method will encrypt your data with a key
|
||||||
generated from a password or PIN. The main advantage here is that this will work with
|
generated from a password or PIN. The main advantage here is that this will work with
|
||||||
external backup solutions (like Titanium) and is much less failure-prone than the KeyStore.
|
external backup solutions (like Titanium) and is much less failure-prone than the KeyStore.
|
||||||
|
|
Loading…
Reference in a new issue