diff options
author | Silvio Rhatto <rhatto@riseup.net> | 2013-08-17 14:26:29 -0300 |
---|---|---|
committer | Silvio Rhatto <rhatto@riseup.net> | 2013-08-17 14:26:29 -0300 |
commit | c95bf5120b8e228948df3e5ae6efbbb18b7a468b (patch) | |
tree | 4ec3cc0abe37eaba2858fd0a8bfe6937b5e4fa51 | |
parent | be0cc7c6e932896178c128ab9e36cb964d33dc00 (diff) | |
download | keyringer-c95bf5120b8e228948df3e5ae6efbbb18b7a468b.tar.gz keyringer-c95bf5120b8e228948df3e5ae6efbbb18b7a468b.tar.bz2 |
Disambiguate keys/secrets
-rw-r--r-- | index.mdwn | 26 |
1 files changed, 13 insertions, 13 deletions
@@ -65,52 +65,52 @@ Fill it with your friends key IDs. Now encrypt a secret just for then: In other words, if keyringer finds a recipient file matching a given path, it will use it instead of the global recipients file. -Managing keys +Managing secrets ---------------- -Each key has a corresponding file in your keys subdirectory. +Each secret has a corresponding file in your `keys` subdirectory. -keyringer is agnostic about how you store your secrets. You may choose to have -one key file that contains one line for each secret, e.g. a single file called +Keyringer is agnostic about how you store your secrets. You may choose to have +one encrypted file that contains one line for each secret, e.g. a single file called secrets with lines such as: emma : root : secret1 emma - /dev/hda : : secret2 -Or you may also have a different key file for each secret, e.g. a file called +Or you may also have a different encrypted file for each secret, e.g. a file called emma.root that contains the root passphrase for the server named emma and another called emma.hda with the passphrase to decrypt /dev/hda on emma. -Encrypting a key +Encrypting a secret keyringer <keyring> encrypt <file> -Encrypting a key from a file +Encrypting a secret from a file keyringer <keyring> encrypt <plaintext-file> <file> -Decrypting a key (only to stdout) +Decrypting a secret (only to stdout) keyringer <keyring> decrypt <file> -Re-encrypting a key or the whole repository +Re-encrypting a secret or the whole repository keyringer <keyring> recrypt [file] -Appending information to a key +Appending information to a secret keyringer <keyring> append <file> -Editing a key +Editing a secret -To edit a key, use +To edit a secret, use keyringer <keyring> edit <file> Use this option with caution as it keeps temporary unencrypted data into keyringer temp folder and at your editor's temp files. -Listing keys +Listing secrets keyringer <keyring> ls [arguments] |