


PGP(1)                     User Manual                     PGP(1)


NNAAMMEE
       PGP - A suite of tools for encrypting, decrypting and ver
       ifying messages.

DDEESSCCRRIIPPTTIIOONN
       There are two files in this  package,  but  several  addi
       tional  modes  of  operation  are  available  via symbolic
       links:

              ppggpp(1) is the main cryptographic engine of the  PGP
              package.   However,  invoking  it  as itself merely
              prints a usage summary.

              ppggppee(1) is executed  to  encrypt,  or  encrypt  and
              sign, files.  It is a link to ppggpp(1).

              ppggppss(1)  is  executed  to only sign files.  It is a
              link to ppggpp(1).

              ppggppvv(1) is  executed  to  only  verify  or  decrypt
              signed or encrypted files.  It is a link to ppggpp(1).

              ppggppkk(1) is the key management application, which is
              used  to  generate, retrieve and send keys, as well
              as manage trust.

       Public key cryptography must be fully  understood  by  the
       user to be useful.  A successful PGP user must be familiar
       with public key cryptography in  general,  and  some  PGP-
       specific concepts (such as the web of trust).  If you feel
       comfortable with your own level of knowledge on this  sub
       ject,  your  first  step is probably going to be to invoke
       ppggppkk(1) to generate a key.  Additionally, a page  by  Phil
       Zimmermann  on  the importance of cryptography is included
       in ppggpp--iinnttrroo(7).

FFIILLEESS
       _~_/_._p_g_p_/_p_g_p_._c_f_g
              User-specific  configuration  file.   In   previous
              releases,  this  file  was  called _c_o_n_f_i_g_._t_x_t.  See
              ppggpp..ccffgg(5) for further details.

MMIIGGRRAATTIIOONN
       Users migrating from earlier versions of PGP will need  to
       manually migrate the following configuration files:

              _~_/_._p_g_p_/_c_o_n_f_i_g_._t_x_t is now _~_/_._p_g_p_/_p_g_p_._c_f_g.  This file
              may be copied manually.  If  not  copied,  internal
              defaults  will  be  used.   This  file  is  largely
              unchanged in 5.0.  See ppggpp..ccffgg(5) for more informa
              tion on this file.

              _~_/_._p_g_p_/_p_u_b_r_i_n_g_._p_g_p  is now _~_/_._p_g_p_/_p_u_b_r_i_n_g_._p_k_r.  You
              may copy your old public keyring, or allow  5.0  to



PGP                      JULY 1997 (v5.0)                       1





PGP(1)                     User Manual                     PGP(1)


              generate a new keyring for you.

              _~_/_._p_g_p_/_s_e_c_r_i_n_g_._p_g_p  is now _~_/_._p_g_p_/_s_e_c_r_i_n_g_._s_k_r.  You
              may copy your old private keyring.  Even if you  do
              this,   you   are  encouraged  to  generate  a  new
              DSS/Diffie-Hellman key to allow communication  with
              all 5.0 users.

              _~_/_._p_g_p_/_l_a_n_g_u_a_g_e_._t_x_t  is  now _~_/_._p_g_p_/_l_a_n_g_u_a_g_e_5_0_._t_x_t.
              This file should nnoott be copied from  your  previous
              installation, as it is completely different in 5.0.
              If this file is not present, internal defaults will
              be used.












































PGP                      JULY 1997 (v5.0)                       2





PGP(1)                     User Manual                     PGP(1)


AAUUTTHHOORRSS
       A cast of thousands.  This is, of course, derived directly
       from the work of Phil R. Zimmermann <prz@pgp.com>.   Major
       contributors to this release include:

       Unix Development
                   Derek Atkins <warlord@MIT.EDU>
                   Hal Finney <hal@pgp.com>
                   Mark McArdle <markm@pgp.com>
                   Brett A. Thomas <quark@baz.com>
                   Mark Weaver <mhw@pgp.com>

       Be Development
                   Mark Elrod <elrod@pgp.com>
                   Brett A. Thomas <quark@baz.com>

       Library Development
                   Derek Atkins <warlord@MIT.EDU>
                   Colin Plumb <colin@pgp.com>
                   Hal Finney <hal@pgp.com>
                   Mark Weaver <mhw@pgp.com>

       Unix Beta Testing
                   Steve Gilbert <darkelf@redcloud.org>
                   Mike Shappe <mshappe@jeeves.net>

       Man Pages
                   Brett A. Thomas <quark@baz.com>

BBUUGGSS
       Keyserver support should be more informative with  unknown
       protocols.

       URL parsing uses static buffers and is vulnerable to over
       flow attacks.

       The PAGER directive in pgp.cfg doesn't work.

       The -b option to ppggppvv(1) is not implemented.  This  option
       allowed  the  "breaking"  of signed files into a signature
       and a file (effectively,  a  retroactive  detached  signa
       ture).

       ppggppvv  --mm  ("more"  mode) and "eyes-only" decryption is not
       displaying properly.  It is suggested that your  pipe  the
       output of ppggppvv(1) into your pager of preference until this
       is fixed.

       ppggppkk(1) doesn't pay attention  to  the  ++ffoorrccee  option  to
       force file overwrite; it stops to ask for confirmation.

       Multipart  armoring  doesn't  handle all possible permuta
       tions - specifically, it does not work properly if all the
       sections  are in one file, or only the first file is named



PGP                      JULY 1997 (v5.0)                       3





PGP(1)                     User Manual                     PGP(1)


       on the command line.

       There is currently no way to specify just a secret or pub
       lic keyring for an operation.

       ppggpp  ----vveerrssiioonn doesn't work.  Use ppggppkk ----vveerrssiioonn or one of
       the other commands, instead.

       ppggppvv --pp, to "preserve" the original input filename, is not
       yet supported.

       There  are a number of bugs when specifying filenames end
       ing in digits; the general result is that the default out
       put filename is not what might be expected (i.e., ppggppee --ssaa
       ffoooo11 results in an output suggestion of _f_o_o_1_._a_s_c_._1 instead
       of  _f_o_o_1_._a_s_c,  as  expected).   It is conjectured that the
       user interface is becoming confused and invoking the rules
       used to generate multi-part ASCII armor filenames.

       Configuration  option  _T_Z_f_i_x doesn't allow specifying non-
       mainstream values, such as --442200 or 3300.

       ppggppkk --ee does not ask about marking a new  userid  as  pri
       mary.

       ppggppkk --aa should accept a key on stdin, but does not.

       ppggppkk  is,  in  some instances, overwriting the "previously
       encrypted to invalid key" flag on some keys.


SSEEEE AALLSSOO
       ppggppee(1),  ppggppvv(1),  ppggppss(1),  ppggppkk(1),  ppggpp..ccffgg(5),   ppggpp--
       iinntteeggrraattiioonn(7),  ppggpp--iinnttrroo(7), http://www.pgp.com (US ver
       sions) and http://www.pgpi.com (International versions)






















PGP                      JULY 1997 (v5.0)                       4


