Do not use ImportKeysListFragment for Security Token import, fixes #1959. Also introduces radio button to import key information from file
This commit is contained in:
@@ -1576,9 +1576,10 @@
|
||||
<string name="security_token_status_unbound">"Security Token matches, can be bound to key"</string>
|
||||
<string name="security_token_status_partly">"Security Token matches, partly bound to key"</string>
|
||||
<string name="security_token_create">"Hold Security Token against the back of your device."</string>
|
||||
<string name="security_token_reset_or_import">"This Security Token already contains a key. You can import the key using the cloud or reset the Security Token."</string>
|
||||
<string name="security_token_reset_or_import">"This Security Token already contains a key. To use it, we need additional key information. These information can be searched on a keyserver or imported from a file."</string>
|
||||
<string name="btn_reset">"Reset"</string>
|
||||
<string name="security_token_import_radio">"Import key"</string>
|
||||
<string name="security_token_import_radio">"Search key information on keyserver"</string>
|
||||
<string name="security_token_file_radio">"Import key information from file"</string>
|
||||
<string name="security_token_reset_radio">"Reset Security Token"</string>
|
||||
<string name="security_token_reset_warning">"Resetting the Security Token completely destroys the keys on it. Afterwards, you will not be able to decrypt messages/files encrypted with this key!"</string>
|
||||
<string name="snack_security_token_other">Different key stored on Security Token!</string>
|
||||
|
||||
Reference in New Issue
Block a user