read.me

pgp加密例子

PGP Open Encryptor Interface 1.1 for WinPMail 2.23 and above.
Copyright 1995 by John Navas, All Rights Reserved.

The author grants explicit permission for the source code to be used
or modified as required, subject only to the conditions that the
copyright notices are preserved; that the source code not be used in
any product distributed in competition with this product; and that by
using this code you agree that the code is provided without warranty
of any kind, either explicit or implied, and you use it at your own
risk.

NOTE:  The latest information on and the latest version of
this interface is always available on the World Wide Web at
http://web.aimnet.com/~jnavas/winpmail.htm

WARNING:  THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF
ANY KIND.  SUPPORT IS NOT AVAILABLE.  USE AT YOUR OWN RISK.

AUTHOR'S NOTE:  For real security you should NEVER use encryption
modules that are not provided in SOURCE CODE form.  Otherwise, you
have NO WAY OF KNOWING IF THE MODULE ITSELF IS COMPROMISING YOUR
SECURITY.

This module implements an interface to Pretty Good Privacy (tm)
and (c) Copyright 1990-1994 Philip Zimmermann. All rights reserved.

PGP information is available at http://www.mantis.co.uk/pgp/pgp.html
The MIT distribution of PGP is at ftp://net-dist.mit.edu:/pub/PGP/
ViaCrypt (commercial version of PGP) is at http://www.viacrypt.com/
The International PGP Home Page is at http://www.ifi.uio.no/~staalesc/PGP/

This interface is designed to work only with Pegasus Mail for Windows
Version 2.23 and above, one of the very best email packages, and one
that is completely free (as is this interface).  Information on
Pegasus Mail is available at http://www.cuslm.ca/pegasus/

Release notes for PGP Open Encryptor Interface version 1.1:

1.  Substantially updated the documentation (including adding
    basic use instructions and troubleshooting sections).
2.  Fixed a problem where encrypted messages that do not actually
    contain encrypted material would be blank in the message Reader.
3.  Substantially improved error-checking and reporting.
4.  Append an advisory text string to a decrypted message (as well
    as the appropriate system sound) if and only if a digital
    signature is found.  (I hated to do this, but I got tired of
    explaining that the digital signature is invisible in decrypted
    messages, and there was no other good way to notify the user.)

Release notes for PGP Open Encryptor Interface version 1.01:

1.  Fixed a problem where signature verification reported that no
    signature could be found when the real condition was that no
    key could be found to verify the signature.

General Release notes:

1.  Only public key cryptography is supported in this release, NOT
    conventional cryptography.
2.  Basic Key Management functions are implemented:
    a.  To add a public key block contained in a message to your Key
        Ring, either Open or select the message before invoking Key
        Management.  (If a public key block is placed in a digitally
        signed and/or encrypted message, it will not be recognized
        automatically by this interface.)  You can also invoke Key
        Management and paste a public key block into the dialog from
        the Windows Clipboard (which does of course work with a
        signed and/or encrypted message).
    b.  You can check to see if a given email address is on your Key
        Ring -- just paste the email address (without the name) into
        the dialog box control.
    No other Key Management functions are implemented at this time.
3.  Both digital signing and signature verification are implemented:
    a.  If a secret pass phrase is needed (and not provided in
        the PGPPASS environment variable), it MUST be provided each
        time in the WinPMail Password field.
    b.  Please note that signature verification of non-encrypted
        messages is a strictly *manual* process -- you must expliticly
        use the WinPMail menu.  This is a characteristic of WinPMail,
        NOT this interface.
4.  When encrypting:
    a.  The recipient email address (e.g., [e-mail]) will
        normally select the appropriate public key automatically, but
        it may be overridden with an entry in the WinPMail Password
        field if the message is not also being digitally signed.  
    b   You should NEVER enter a secret pass phrase when encrypting
        unless you are also signing the message.  (See use
        instructions below.)
    c.  Your recipient may need to add also-known-as entries to
        his/her public key to ensure that you match on various forms
        of email addresses (e.g., also known as
        [e-mail]).
5.  If encryption or signing fails (e.g., because the recipient is not
    on your key ring, or because your secret pass phrase was
    incorrect), an empty message will be sent.  This is a
    characteristic of WinPMail, NOT this interface.
6.  Copies to self of encrypted and/or signed messages are NOT
    encrypted and/or signed.  This is a characteristic of WinPMail, NOT
    this interface.  (If you want an encrypted and/or signed copy, BCC
    yourself.)
7.  It is normally NOT possible for you to decrypt message that you
    have encrypted for someone else (since you do not have that
    person's secret key).  However, you can establish a master
    decryption key by setting the PGPJNKEY environment variable to a
    string needed to select the appropriate public key (yours or not).
    TEST FOR PROPER OPERATION (BY DECRYPTING A MESSAGE ENCRYPTED FOR
    SOMEONE ELSE) BEFORE YOU DEPEND ON IT!  It may be a good idea to
    add an also-known-as alias just for this purpose.
8.  The Cancel button does not work on the Decryption dialog box.
    This is a characteristic of WinPMail, NOT this interface.
9.  When you do a Find on a folder, WinPMail puts up the Decryption key
    dialog for every encrypted message, even when you are only
    searching headers, which can make the process painful.  This is a
    characteristic of WinPMail, NOT this interface.
10. Attachments to encrypted messages are NOT supported.  (Outgoing
    attachments to encrypted messages are NOT encrypted, and incoming
    binary attachments are corrupted.)  This is a characteristic of
    WinPMail, NOT this interface.
11. Windows 3.10, Windows for Workgroups 3.11, and Windows 95 are
    supported.  Windows NT and OS/2 have NOT been tested and are NOT
    currently supported.  (Windows NT is likely to work, but OS/2 in
    not likely to work because of subtle incompatibilities in IBM's
    implementation of certain Windows API functions.)  USE THEM AT YOUR
    OWN RISK.
12. MIT PGP 2.6.2 is supported in this release.  Other versions of PGP
    have NOT been tested and are NOT currently supported.  (The
    international version of PGP 2.6.2 is likely to work.)  ViaCrypt PGP
    has NOT been tested for this release, but is expected to be
    supported in a subsequent release.  USE THEM AT YOUR OWN RISK.
13. Reassembly and decryption of multiple-part PGP messages is NOT
    supported.
14. PGP messages sent by other WinPMail Open Encryptor PGP interfaces
    may not trigger this interface.  (Other PGP sources should not be a
    problem.)  This is a characteristic of WinPMail, NOT this
    interface.
15. A good way to set the PGPPASS environment variable is to type it into
    RAM in a step in your AUTOEXEC.BAT file (so that it's not stored on
    disk).  A good way to do that is with the freeware 'setenv'
    <ftp://ftp.uoknor.edu/mirrors/SimTel/msdos/envutil/stnvjw25.zip> e.g.,
    setenv PGPPASS %prompt %noecho Enter your secret PGP passphrase:
16. Be careful not to use too long a "secret pass phrase" if you're going
    to type it in each time -- because of the DOS command line length 
    limit, very long secret pass phrases may be truncated (and therefore
    fail).

To install the PGP Open Encryptor Interface:

1.  UnZIP in a subdirectory of FORMS called PGPJN
    (e.g., \PMAIL\FORMS\PGPJN).  Do NOT use a different name -- it MUST
    be exactly PGPJN!
2.  Copy the PGPJNP.FFF file up to your WinPMail directory (e.g.,
    \PMAIL).
3.  Make sure that you have set the environment variable TEMP (in your
    AUTOEXEC.BAT file) to point to a valid hard disk directory where
    this interface can create temporary files.
4.  Make sure that PGP is installed correctly, and that the PGPPATH