|
|
1.1.1.2 ! root 1: Here's a quick summary of PGP v2.2 commands. ! 2: 1.1 root 3: 4: To encrypt a plaintext file with the recipient's public key: 5: pgp -e textfile her_userid 6: 7: To sign a plaintext file with your secret key: 8: pgp -s textfile [-u your_userid] 9: 10: To sign a plaintext file with your secret key, and then encrypt it 11: with the recipient's public key: 12: pgp -es textfile her_userid [-u your_userid] 13: 14: To encrypt a plaintext file with just conventional cryptography, type: 15: pgp -c textfile 16: 17: To decrypt an encrypted file, or to check the signature integrity of a 18: signed file: 19: pgp ciphertextfile [-o plaintextfile] 20: 1.1.1.2 ! root 21: To encrypt a message for any number of multiple recipients: ! 22: pgp -e textfile userid1 userid2 userid3 1.1 root 23: 24: --- Key management commands: 25: 26: To generate your own unique public/secret key pair: 27: pgp -kg 28: 29: To add a public or secret key file's contents to your public or 30: secret key ring: 31: pgp -ka keyfile [keyring] 32: 33: To extract (copy) a key from your public or secret key ring: 34: pgp -kx userid keyfile [keyring] 35: or: pgp -kxa userid keyfile [keyring] 36: 37: To view the contents of your public key ring: 38: pgp -kv[v] [userid] [keyring] 39: 40: To view the "fingerprint" of a public key, to help verify it over 41: the telephone with its owner: 42: pgp -kvc [userid] [keyring] 43: 44: To view the contents and check the certifying signatures of your 45: public key ring: 46: pgp -kc [userid] [keyring] 47: 48: To edit the userid or pass phrase for your secret key: 49: pgp -ke userid [keyring] 50: 51: To edit the trust parameters for a public key: 52: pgp -ke userid [keyring] 53: 54: To remove a key or just a userid from your public key ring: 55: pgp -kr userid [keyring] 56: 57: To sign and certify someone else's public key on your public key ring: 58: pgp -ks her_userid [-u your_userid] [keyring] 59: 60: To remove selected signatures from a userid on a keyring: 61: pgp -krs userid [keyring] 62: 1.1.1.2 ! root 63: To permanently revoke your own key, issuing a key compromise 1.1 root 64: certificate: 65: pgp -kd your_userid 66: 1.1.1.2 ! root 67: To disable or reenable a public key on your own public key ring: ! 68: pgp -kd userid ! 69: 1.1 root 70: --- Esoteric commands: 71: 72: To decrypt a message and leave the signature on it intact: 73: pgp -d ciphertextfile 74: 75: To create a signature certificate that is detached from the document: 76: pgp -sb textfile [-u your_userid] 77: 78: To detach a signature certificate from a signed message: 79: pgp -b ciphertextfile 80: 81: --- Command options that can be used in combination with other 82: command options (sometimes even spelling interesting words!): 83: 84: To produce a ciphertext file in ASCII radix-64 format, just add the 85: -a option when encrypting or signing a message or extracting a key: 86: pgp -sea textfile her_userid 87: or: pgp -kxa userid keyfile [keyring] 88: 89: To wipe out the plaintext file after producing the ciphertext file, 90: just add the -w (wipe) option when encrypting or signing a message: 91: pgp -sew message.txt her_userid 92: 93: To specify that a plaintext file contains ASCII text, not binary, and 94: should be converted to recipient's local text line conventions, add 95: the -t (text) option to other options: 96: pgp -seat message.txt her_userid 97: 98: To view the decrypted plaintext output on your screen (like the 99: Unix-style "more" command), without writing it to a file, use 100: the -m (more) option while decrypting: 101: pgp -m ciphertextfile 102: 103: To specify that the recipient's decrypted plaintext will be shown 104: ONLY on her screen and cannot be saved to disk, add the -m option: 105: pgp -steam message.txt her_userid 106: 107: To recover the original plaintext filename while decrypting, add 108: the -p option: 109: pgp -p ciphertextfile 110: 111: To use a Unix-style filter mode, reading from standard input and 112: writing to standard output, add the -f option: 113: pgp -feast her_userid <inputfile >outputfile 114:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.