lysann/passforios
1
0
Fork 0
Code Issues Pull requests Activity

Polish instructions (#514)

Browse source 
Signed-off-by: Hörmetjan Yiltiz <hyiltiz@gmail.com>
This commit is contained in:
Hörmet Yiltiz 2021-09-30 13:55:20 -04:00 • committed by GitHub
parent cddcb9fcc1
commit e3fbddbe92
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 33 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

42
pass/en.lproj/Localizable.strings
View file

@ -299,21 +299,45 @@ to get the key in this specific format. Subsequently, copy it to a location acce
"GpgAsciiArmorCopyExplanation." = "GnuPG supports the command-line option \"-a\" that causes output to be generated in an ASCII-armored format similar to unencoded documents rather than the binary format. Use "GpgAsciiArmorCopyExplanation." = "GnuPG supports the command-line option \"-a\" that causes output to be generated in an ASCII-armored format similar to unencoded documents rather than the binary format. Use
$ gpg --export -a KEY_ID $ gpg --list-keys
$ gpg --export-secret-keys -a KEY_ID
to get the public and the private key in this specific format. The clipboard will be cleared 45s after pasting."; to identify your encryption (E) subkey, then use:
$ gpg --export -a KEY_ID! > subkey.pub
$ gpg --export-secret-subkeys -a KEY_ID! > subkey
to get the public and the encryption private subkeys in this specific format. Check that no Authentication subkey is accidentally exported, using:
$ gpg --show-key subkey
The clipboard will be cleared 45s after pasting.";
"GpgAsciiArmorServerExplanation." = "GnuPG supports the command-line option \"-a\" that causes output to be generated in an ASCII-armored format similar to unencoded documents rather than the binary format. Use "GpgAsciiArmorServerExplanation." = "GnuPG supports the command-line option \"-a\" that causes output to be generated in an ASCII-armored format similar to unencoded documents rather than the binary format. Use
$ gpg --export -a KEY_ID $ gpg --list-keys
$ gpg --export-secret-keys -a KEY_ID
to get the public and the private key in this specific format. Subsequently, copy them to your secured key server."; to identify your encryption (E) subkey, then use:
$ gpg --export -a KEY_ID! > subkey.pub
$ gpg --export-secret-subkeys -a KEY_ID! > subkey
to get the public and the encryption private subkeys in this specific format. Check that no Authentication subkey is accidentally exported, using:
$ gpg --show-key subkey
Finally, copy them to your secured key server.";
"GpgAsciiArmorFileExplanation." = "GnuPG supports the command-line option \"-a\" that causes output to be generated in an ASCII-armored format similar to unencoded documents rather than the binary format. Use "GpgAsciiArmorFileExplanation." = "GnuPG supports the command-line option \"-a\" that causes output to be generated in an ASCII-armored format similar to unencoded documents rather than the binary format. Use
$ gpg --export -a KEY_ID $ gpg --list-keys
$ gpg --export-secret-keys -a KEY_ID
to get the public and the private key in this specific format. Subsequently, copy them to a location accessible by the Files app."; to identify your encryption (E) subkey, then use:
$ gpg --export -a KEY_ID! > subkey.pub
$ gpg --export-secret-subkeys -a KEY_ID! > subkey
to get the public and the encryption private subkeys in this specific format. Check that no Authentication subkey is accidentally exported, using:
$ gpg --show-key subkey
Finally, copy them to a location accessible by the Files app.";