# $EPIC: encrypt,v 1.7 2002/01/24 19:16:26 crazyed Exp $
Synopsis:
   encrypt [<nickname|channel> [<key> [<program>]]]
   encrypt [<channel,sourcenick!user@host> [<key> [<program>]]]

Description:
   This allows you to maintain an encrypted conversation with a person
   or channel.  Any messages you send to the specified target will
   automatically be encrypted.  If the recipient has likewise specified
   the proper encryption key for you, the incoming message will
   automatically be decrypted.  Both parties must use the same key for
   the messages to be decrypted.  Anyone receiving an encrypted message
   without specifying the proper key will instead see "[ENCRYPTED
   MESSAGE]" on their screen.

   If program is given, each message will be filtered through that
   program for encryption or decryption. For details on how to write
   such a program, see the epic-crypt-gpg* scripts in the script
   directory of the distribution.  To use these scripts, put them in
   your path, and make them executable.

   The second form of the command is available for decryption only,
   and may be a wildcard string.  This permits different people on
   a channel to use different keys.  On decryption a check is made
   against the second form of the command, and if it fails, the first
   is used.  The comma is _required_ in this form.

   If no arguments are specified, a list of nicknames (or channels)
   that encrypted messages are being sent to is shown, along with their
   respective keys.  If only a nickname or channel is given, the
   encrypted session with that target is ended.

Examples:
   To start an encrypted session with JoeBob using the key "foobar":
      /encrypt joebob foobar

   To start an encrypted session with channel #blah using key "booya":
      /encrypt #blah booya

   To list your current encrypted sessions:
      /encrypt

   To end your encrypted session with JoeBob:
      /encrypt joebob

   JoeBob on channel #blah is being rebellious and using a different
   key and encryption method and you still wish to see what everybody
   is saying.  After this, the encryption key you will use to send to
   the channel will still be 'booya':
      /encrypt #blah,joebob!* fludle epic-crypt-gpg-aa

   You are being rebelious on #blah by using a different key, and you
   still wish to see what everybody using the old key is saying:
      /encrypt #blah,* oldkey
      /encrypt #blah mykey

Other Notes:
   IrcII's built-in encryption is fine for most purposes, but since the
   raw algorithm is hardcoded into the client, it's not terribly secure.
   It is generally suitable to deter prying eyes, but is certainly not
   suitable for genuinely sensitive transactions.

   Encrypted messages may be sent across DCC CHAT connections.  However,
   non-EPIC3 clients will probably be confused by them.
