head	1.57;
access;
symbols
	DEVEL-BRANCH-1-1:1.57
	V1-0-0:1.56
	V0-9-11:1.55
	V0-9-10:1.53
	V0-9-9:1.52
	V0-9-8:1.50
	V0-9-7:1.47
	V0-9-6:1.47
	V0-9-5:1.45
	V0-9-4:1.44
	V0-9-3:1.43
	V0-9-2:1.42
	V0-9-1:1.40
	V0-9-0:1.40
	V0-4-5:1.37
	V0-4-4:1.37
	V0-4-3:1.35
	V0-4-2:1.34
	V0-4-1:1.31
	V0-4-0:1.29
	V0-3-5:1.28
	V0-3-4:1.28
	V0-3-3:1.28
	V0-3-2:1.23
	V0-3-1:1.22
	V0-3-0:1.22
	V0-2-19:1.21
	V0-2-18:1.20
	V0-2-17:1.20
	V0-2-15:1.17
	V0-2-10:1.15
	V-0-2-8:1.14
	V0-2-6:1.12
	V0-2-0:1.8
	V0-1-0:1.5
	V0-0-0:1.5;
locks; strict;
comment	@# @;


1.57
date	99.09.18.07.18.02;	author wkoch;	state Exp;
branches;
next	1.56;

1.56
date	99.09.06.18.10.08;	author wkoch;	state Exp;
branches;
next	1.55;

1.55
date	99.09.02.14.50.28;	author wkoch;	state Exp;
branches;
next	1.54;

1.54
date	99.08.31.15.30.01;	author wkoch;	state Exp;
branches;
next	1.53;

1.53
date	99.08.04.08.45.07;	author wkoch;	state Exp;
branches;
next	1.52;

1.52
date	99.07.23.12.02.47;	author wkoch;	state Exp;
branches;
next	1.51;

1.51
date	99.07.14.17.47.01;	author wkoch;	state Exp;
branches;
next	1.50;

1.50
date	99.06.26.10.22.47;	author wkoch;	state Exp;
branches;
next	1.49;

1.49
date	99.06.16.18.25.33;	author wkoch;	state Exp;
branches;
next	1.48;

1.48
date	99.06.02.12.25.54;	author wkoch;	state Exp;
branches;
next	1.47;

1.47
date	99.05.06.12.25.58;	author wkoch;	state Exp;
branches;
next	1.46;

1.46
date	99.04.09.10.34.33;	author wkoch;	state Exp;
branches;
next	1.45;

1.45
date	99.03.20.11.56.56;	author wkoch;	state Exp;
branches;
next	1.44;

1.44
date	99.03.08.19.50.01;	author koch;	state Exp;
branches;
next	1.43;

1.43
date	99.02.10.16.22.17;	author koch;	state Exp;
branches;
next	1.42;

1.42
date	99.01.13.11.51.39;	author koch;	state Exp;
branches;
next	1.41;

1.41
date	99.01.12.10.20.11;	author koch;	state Exp;
branches;
next	1.40;

1.40
date	98.12.23.16.16.48;	author koch;	state Exp;
branches;
next	1.39;

1.39
date	98.12.23.12.41.10;	author koch;	state Exp;
branches;
next	1.38;

1.38
date	98.12.17.17.35.48;	author koch;	state Exp;
branches;
next	1.37;

1.37
date	98.11.20.19.22.51;	author koch;	state Exp;
branches;
next	1.36;

1.36
date	98.11.13.19.41.32;	author koch;	state Exp;
branches;
next	1.35;

1.35
date	98.11.08.17.23.09;	author koch;	state Exp;
branches;
next	1.34;

1.34
date	98.10.18.15.21.10;	author koch;	state Exp;
branches;
next	1.33;

1.33
date	98.10.16.15.59.56;	author wk;	state Exp;
branches;
next	1.32;

1.32
date	98.10.12.20.16.19;	author wk;	state Exp;
branches;
next	1.31;

1.31
date	98.10.07.13.30.36;	author wk;	state Exp;
branches;
next	1.30;

1.30
date	98.09.28.19.25.11;	author wk;	state Exp;
branches;
next	1.29;

1.29
date	98.09.18.15.24.38;	author wk;	state Exp;
branches;
next	1.28;

1.28
date	98.08.08.21.13.58;	author wk;	state Exp;
branches;
next	1.27;

1.27
date	98.08.08.19.26.43;	author wk;	state Exp;
branches;
next	1.26;

1.26
date	98.08.05.16.51.46;	author wk;	state Exp;
branches;
next	1.25;

1.25
date	98.07.29.19.34.37;	author wk;	state Exp;
branches;
next	1.24;

1.24
date	98.07.14.17.10.10;	author wk;	state Exp;
branches;
next	1.23;

1.23
date	98.07.07.14.39.39;	author wk;	state Exp;
branches;
next	1.22;

1.22
date	98.06.25.11.08.10;	author wk;	state Exp;
branches;
next	1.21;

1.21
date	98.05.29.11.53.40;	author wk;	state Exp;
branches;
next	1.20;

1.20
date	98.05.04.18.49.11;	author wk;	state Exp;
branches;
next	1.19;

1.19
date	98.04.30.14.05.40;	author wk;	state Exp;
branches;
next	1.18;

1.18
date	98.04.14.17.50.45;	author wk;	state Exp;
branches;
next	1.17;

1.17
date	98.04.09.11.18.59;	author wk;	state Exp;
branches;
next	1.16;

1.16
date	98.03.09.21.43.45;	author wk;	state Exp;
branches;
next	1.15;

1.15
date	98.02.26.16.56.11;	author wk;	state Exp;
branches;
next	1.14;

1.14
date	98.02.24.18.50.02;	author wk;	state Exp;
branches;
next	1.13;

1.13
date	98.02.17.20.48.46;	author wk;	state Exp;
branches;
next	1.12;

1.12
date	98.02.13.20.58.35;	author wk;	state Exp;
branches;
next	1.11;

1.11
date	98.02.09.17.43.29;	author wk;	state Exp;
branches;
next	1.10;

1.10
date	98.01.28.16.09.30;	author wk;	state Exp;
branches;
next	1.9;

1.9
date	98.01.26.22.08.46;	author wk;	state Exp;
branches;
next	1.8;

1.8
date	98.01.25.18.56.25;	author wk;	state Exp;
branches;
next	1.7;

1.7
date	98.01.24.16.32.15;	author wk;	state Exp;
branches;
next	1.6;

1.6
date	98.01.12.10.17.57;	author wk;	state Exp;
branches;
next	1.5;

1.5
date	98.01.05.19.13.07;	author wk;	state Exp;
branches;
next	1.4;

1.4
date	98.01.02.20.39.58;	author wk;	state Exp;
branches;
next	1.3;

1.3
date	97.12.20.17.23.22;	author wk;	state Exp;
branches;
next	1.2;

1.2
date	97.12.16.19.14.54;	author wk;	state Exp;
branches;
next	1.1;

1.1
date	97.11.18.14.05.34;	author wk;	state Exp;
branches;
next	;


desc
@@


1.57
log
@Setup development branch
@
text
@-----BEGIN PGP SIGNED MESSAGE-----

		    GnuPG - The GNU Privacy Guard
		   -------------------------------
			    Version 1.1

	WARNING:  This is the current development branch
		  of GnuPG.  THIS SHOULD NOT BE USED IN
		  A PRODUCTION ENVIRONMENT.  It will
		  change quite often and may have serious
		  problems.  Use the GnuPG from the stable
		  Branch 1.0.x	for real work.	The next
		  stable release will be 1.2


    GnuPG is GNU's tool for secure communication and data storage.
    It can be used to encrypt data and to create digital signatures.
    It includes an advanced key management facility and is compliant
    with the proposed OpenPGP Internet standard as described in RFC2440.

    GnuPG works best on GNU/Linux or *BSD systems.  Most other Unices
    are also supported but are not as well tested as the Free Unices.
    See http://www.gnupg.org/gnupg.html#supsys for a list of systems
    which are known to work.

    See the file COPYING for copyright and warranty information.

    Because GnuPG does not use use any patented algorithm it cannot be
    compatible with PGP2 versions.  PGP 2.x uses only IDEA (which is
    patented worldwide) and RSA (which is patented in the United States
    until Sep 20, 2000).

    The default algorithms are DSA and ElGamal.  ElGamal for signing
    is still available, but because of the larger size of such
    signatures it is deprecated (Please note that the GnuPG
    implementation of ElGamal signatures is *not* insecure).  Symmetric
    algorithms are: 3DES, Blowfish, CAST5 and Twofish (GnuPG does not
    yet create Twofish encrypted messages because there is no agreement
    in the OpenPGP WG on how to use it together with a MDC algorithm)
    Digest algorithms available are MD5, RIPEMD160 and SHA1.


    Installation
    ------------

    Please read the file INSTALL!

    Here is a quick summary:

    1) Check that you have unmodified sources.	The below on how to do this.
       Don't skip it - this is an important step!

    2)	Unpack the TAR.  With GNU tar you can do it this way:
	"tar xzvf gnupg-x.y.z.tar.gz"

    3) "cd gnupg-x.y.z"

    4)	"./configure"

    5) "make"

    6) "make install"

    7) You end up with a "gpg" binary in /usr/local/bin.
       Note: Because some old programs rely on the existence of a
       binary named "gpgm" (which was build by some Beta versions
       of GnuPG); you may want to install a symbolic link to it:
       "cd /usr/local/bin; ln -s gpg gpgm"

    8) To avoid swapping out of sensitive data, you can install "gpg" as
       suid root.  If you don't do so, you may want to add the option
       "no-secmem-warning" to ~/.gnupg/options


    How to Verify the Source
    ------------------------

    In order to check that the version of GnuPG which you are going to
    install is an original and unmodified one, you can do it in one of
    the following ways:

    a) If you already have a trusted Version of GnuPG installed, you
       can simply check the supplied signature:

	$ gpg --verify gnupg-x.y.z.tar.gz.asc

       This checks that the detached signature gnupg-x.y.z.tar.gz.asc
       is indeed a a signature of gnupg-x.y.z.tar.gz.  The key used to
       create this signature is:

       "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"

       If you do not have this key, you can get it from the source in
       the file g10/pubring.asc (use "gpg --import g10/pubring.gpg" to
       add it to the keyring) or from any keyserver.  You have to make
       sure that this is really the key and not a faked one. You can do
       this by comparing the output of:

		$ gpg --fingerprint 0x57548DCD

       with the elsewhere published fingerprint, or - if you are able to
       _positively_ verify the signature of this README file - with
       this fingerprint: "6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

       Please note, that you have to use an old version of GnuPG to
       do all this stuff.  *Never* use the version which you are going
       to check!


    b) If you have a trusted Version of PGP 2 or 5 installed, you
       can check the supplied PGP 2 signature:

	$ pgp gnupg-x.y.z.tar.gz.sig gnupg-x.y.z.tar.gz

       This checks that the detached signature gnupg-x.y.z.tar.gz.sig
       is indeed a a signature of gnupg-x.y.z.tar.gz.  Please note,
       that this signature has been created with a RSA signature and
       you probably can't use this method (due to legal reasons) when
       you are in the U.S.  The key used to create this signature is
       the same as the one used to sign this README file.  It should be
       available at the keyservers and is also included in the source
       of GnuPG in g10/pubring.asc.

       "pub   768R/0C9857A5 1995-09-30 Werner Koch <werner.koch@@guug.de>"

       The fingerprint of this key is published in printed form in the
	  "Global Trust Register for 1998", ISBN 0-9532397-0-5.


    c) If you don't have any of the above programs, you have to verify
       the MD5 checksum:

	$ md5sum gnupg-x.y.z.tar.gz.sig

       This should yield an output similar_to this:

	fd9351b26b3189c1d577f0970f9dcadc  gnupg-x.y.z.tar.gz

       Now check that this checksum is _exactly_ the same as the one
       published via the announcement list and probably via Usenet.



    Documentation
    -------------

    A draft version of the manual is included in the subdirectory doc/gph.
    The supplied version is rendered in HTML and you may access it with any
    browser (e.g.: lynx doc/gpg/index.html).  The GnuPG webpages have a link
    to the latest development version and you may want to read those instead.

    A couple of HOWTO documents are available online; for a listing see:

	http://www.gnupg.org/docs.html#howtos

    A man page with a description of all commands and options gets installed
    along with the program.


    Introduction
    ------------

    Here is a brief overview on how to use GnuPG - it is strongly suggested
    that you read the manual and other information about the use of
    cryptography.  GnuPG is only a tool, secure usage requires that
    YOU KNOW WHAT YOU ARE DOING.

    If you already have a DSA key from PGP 5 (they call them DH/ElGamal)
    you can simply copy the pgp keyrings over the GnuPG keyrings after
    running gpg once to create the correct directory.

    The normal way to create a key is

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for the key parameters, GnuPG needs to gather
    enough noise (entropy) from your system.  If you see no progress
    during key generation you should start some other activities such
    as mouse moves or hitting on the CTRL and SHIFT keys.

    Generate a key ONLY on a machine where you have direct physical
    access - don't do it over the network or on a machine used also
    by others - especially if you have no access to the root account.

    When you are asked for a passphrase use a good one which you can
    easy remember.  Don't make the passphrase too long because you have
    to type it for every decryption or signing; but, - AND THIS IS VERY
    IMPORTANT - use a good one that is not easily to guess because the
    security of the whole system relies on your secret key and the
    passphrase that protects it when someone gains access to your secret
    keyring.  A good way to select a passphrase is to figure out a short
    nonsense sentence which makes some sense for you and modify it by
    inserting extra spaces, non-letters and changing the case of some
    characters - this is really easy to remember especially if you
    associate some pictures with it.

    Next, you should create a revocation certificate in case someone
    gets knowledge of your secret key or you forgot your passphrase

	gpg --gen-revoke your_user_id

    Run this command and store the revocation certificate away.  The output
    is always ASCII armored, so that you can print it and (hopefully
    never) re-create it if your electronic media fails.

    Now you can use your key to create digital signatures

	gpg -s file

    This creates a file "file.gpg" which is compressed and has a
    signature attached.

	gpg -sa file

    Same as above, but creates a file "file.asc" which is ASCII armored
    and and ready for sending by mail.	It is better to use your
    mailers features to create signatures (The mailer uses GnuPG to do
    this) because the mailer has the ability to MIME encode such
    signatures - but this is not a security issue.

	gpg -s -o out file

    Creates a signature of "file", but writes the output to the file
    "out".

    Everyone who knows your public key (you can and should publish
    your key by putting it on a key server, a web page or in your .plan
    file) is now able to check whether you really signed this text

	gpg --verify file

    GnuPG now checks whether the signature is valid and prints an
    appropriate message.  If the signature is good, you know at least
    that the person (or machine) has access to the secret key which
    corresponds to the published public key.

    If you run gpg without an option it will verify the signature and
    create a new file that is identical to the original.  gpg can also
    run as a filter, so that you can pipe data to verify trough it

	cat signed-file | gpg | wc -l

    which will check the signature of signed-file and then display the
    number of lines in the original file.

    To send a message encrypted to someone you can use

	gpg -e -r heine file

    This encrypts "file" with the public key of the user "heine" and
    writes it to "file.gpg"

	echo "hello" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hello\n" and mails it as ASCII armored message
    to the user with the mail address heine.

	gpg -se -r heine file

    This encrypts "file" with the public key of "heine" and writes it
    to "file.gpg" after signing it with your user id.

	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with your alternative user id "Suttner"


    GnuPG has some options to help you publish public keys.  This is
    called "exporting" a key, thus

	gpg --export >all-my-keys

    exports all the keys in the keyring and writes them (in a binary
    format) to "all-my-keys".  You may then mail "all-my-keys" as an
    MIME attachment to someone else or put it on an FTP server. To
    export only some user IDs, you give them as arguments on the command
    line.

    To mail a public key or put it on a web page you have to create
    the key in ASCII armored format

	gpg --export --armor | mail panther@@tiger.int

    This will send all your public keys to your friend panther.

    If you have received a key from someone else you can put it
    into your public keyring.  This is called "importing"

	gpg --import [filenames]

    New keys are appended to your keyring and already existing
    keys are updated. Note that GnuPG does not import keys that
    are not self-signed.

    Because anyone can claim that a public key belongs to her
    we must have some way to check that a public key really belongs
    to the owner.  This can be achieved by comparing the key during
    a phone call.  Sure, it is not very easy to compare a binary file
    by reading the complete hex dump of the file - GnuPG (and nearly
    every other program used for management of cryptographic keys)
    provides other solutions.

	gpg --fingerprint <username>

    prints the so called "fingerprint" of the given username which
    is a sequence of hex bytes (which you may have noticed in mail
    sigs or on business cards) that uniquely identifies the public
    key - different keys will always have different fingerprints.
    It is easy to compare fingerprints by phone and I suggest
    that you print your fingerprint on the back of your business
    card.  To see the fingerprints of the secondary keys, you can
    give the command twice; but this is normally not needed.

    If you don't know the owner of the public key you are in trouble.
    Suppose however that friend of yours knows someone who knows someone
    who has met the owner of the public key at some computer conference.
    Suppose that all the people between you and the public key holder
    may now act as introducers to you.	Introducers signing keys thereby
    certify that they know the owner of the keys they sign.  If you then
    trust all the introducers to have correctly signed other keys, you
    can be be sure that the other key really belongs to the one who
    claims to own it..

    There are 2 steps to validate a key:
	1. First check that there is a complete chain
	   of signed keys from the public key you want to use
	   and your key and verify each signature.
	2. Make sure that you have full trust in the certificates
	   of all the introduces between the public key holder and
	   you.
    Step 2 is the more complicated part because there is no easy way
    for a computer to decide who is trustworthy and who is not.  GnuPG
    leaves this decision to you and will ask you for a trust value
    (here also referenced as the owner-trust of a key) for every key
    needed to check the chain of certificates.	You may choose from:
      a) "I don't know" - then it is not possible to use any
	 of the chains of certificates, in which this key is used
	 as an introducer, to validate the target key.	Use this if
	 you don't know the introducer.
      b) "I do not trust" - Use this if you know that the introducer
	 does not do a good job in certifying other keys.  The effect
	 is the same as with a) but for a) you may later want to
	 change the value because you got new information about this
	 introducer.
      c) "I trust marginally" - Use this if you assume that the
	 introducer knows what he is doing.  Together with some
	 other marginally trusted keys, GnuPG validates the target
	 key then as good.
      d) "I fully trust" - Use this if you really know that this
	 introducer does a good job when certifying other keys.
	 If all the introducer are of this trust value, GnuPG
	 normally needs only one chain of signatures to validate
	 a target key okay. (But this may be adjusted with the help
	 of some options).
    This information is confidential because it gives your personal
    opinion on the trustworthiness of someone else.  Therefore this data
    is not stored in the keyring but in the "trustdb"
    (~/.gnupg/trustdb.gpg).  Do not assign a high trust value just
    because the introducer is a friend of yours - decide how well she
    understands the implications of key signatures and you may want to
    tell her more about public key cryptography so you can later change
    the trust value you assigned.

    Okay, here is how GnuPG helps you with key management.  Most stuff
    is done with the --edit-key command

	gpg --edit-key <keyid or username>

    GnuPG displays some information about the key and then prompts
    for a command (enter "help" to see a list of commands and see
    the man page for a more detailed explanation).  To sign a key
    you select the user ID you want to sign by entering the number
    that is displayed in the leftmost column (or do nothing if the
    key has only one user ID) and then enter the command "sign" and
    follow all the prompts.  When you are ready, give the command
    "save" (or use "quit" to cancel your actions).

    If you want to sign the key with another of your user IDs, you
    must give an "-u" option on the command line together with the
    "--edit-key".

    Normally you want to sign only one user ID because GnuPG
    uses only one and this keeps the public key certificate
    small.  Because such key signatures are very important you
    should make sure that the signatories of your key sign a user ID
    which is very likely to stay for a long time - choose one with an
    email address you have full control of or do not enter an email
    address at all.  In future GnuPG will have a way to tell which
    user ID is the one with an email address you prefer - because
    you have no signatures on this email address it is easy to change
    this address.  Remember, your signatories sign your public key (the
    primary one) together with one of your user IDs - so it is not possible
    to change the user ID later without voiding all the signatures.

    Tip: If you hear about a key signing party on a computer conference
    join it because this is a very convenient way to get your key
    certified (But remember that signatures have nothing to to with the
    trust you assign to a key).


    8 Ways to Specify a User ID
    --------------------------
    There are several ways to specify a user ID, here are some examples.

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string:

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

    * By word match

	"+Heinrich Heine duesseldorf"

      All words must match exactly (not case sensitive) and appear in
      any order in the user ID.  Words are any sequences of letters,
      digits, the underscore and characters with bit 7 set.

    * By the Local ID (from the trust DB):

	"#34"

      This may be used by a MUA to specify an exact key after selecting
      a key from GnuPG (by using a special option or an extra utility)

    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.


    Batch mode
    ----------
    If you use the option "--batch", GnuPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase.  Until we have a better solution (something like ssh-agent),
    you can use the option "--passphrase-fd n", which works like PGP's
    PGPPASSFD.

    Batch mode also causes GnuPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GnuPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or, better, the output of the fd specified with --status-fd to get
    detailed information about the errors.


    How to Get More Information
    ---------------------------

    The primary WWW page is "http://www.gnupg.org"
    The primary FTP site is "ftp://ftp.gnupg.org/pub/gcrypt/"

    See http://www.gnupg.org/mirrors.html for a list of FTP mirrors
    and use them if possible.  You may also find GnuPG mirrored on
    some of the regular GNU mirrors.

    We have some mailing lists dedicated to GnuPG:

	gnupg-announce@@gnupg.org    For important announcements like
				    new versions and  such stuff.
				    This is a moderated list and has
				    very low traffic.
	gnupg-users@@gnupg.org	    For general user discussion and
				    help.
	gnupg-devel@@gnupg.org	    GnuPG developers main forum.

    You subscribe to one of the list by sending mail with a subject
    of "subscribe" to x-request@@gnupg.org, where x is the name of the
    mailing list (gnupg-announce, gnupg-users, etc.).  An archive of
    the mailing lists is available at http://lists.gnupg.org .

    The gnupg.org domain is hosted in Germany to avoid possible legal
    problems (technical advices may count as a violation of ITAR).

    Please direct bug reports to <gnupg-bugs@@gnu.org> or post
    them direct to the mailing list <gnupg-devel@@gnupg.org>.

    Please direct questions about GnuPG to the users mailing list or
    one of the pgp newsgroups; please do not direct questions to one
    of the authors directly as we are busy working on improvements
    and bug fixes.  Both mailing lists are watched by the authors
    and we try to answer questions when time allows us to do so.

    Commercial grade support for GnuPG is available; please see
    the GNU service directory or search other resources.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iQB1AwUBN+M8CB0Z9MEMmFelAQFmggMAuwHxMcQPsS1r2pD1KVZ67qTUeZnSM+wP
daX3wnBgZzxYhzZiuciaFYky6ERC0Er4HVKtSlLBPhY1N1y2d98Se7TTUaUsVY8F
uvGJkK/7ykaHfWgcIbKFb6hlnpy29+mO
=1oCH
-----END PGP SIGNATURE-----
@


1.56
log
@See ChangeLog: Mon Sep  6 19:59:08 CEST 1999  Werner Koch
@
text
@d5 10
a14 1
			    Version 1.0
d520 1
a520 1
Version: GnuPG v0.9.11 (GNU/Linux)
d523 4
a526 4
iQB1AwUBN9QAwB0Z9MEMmFelAQG0XwMAqyH3UR0Jk+dm2ZkVoTqckGqmMMt5IdBN
MlG4g3dau5De8XXHvbQ45cUpU4CC0MOlEuKDp+CKOc+xbzczdH35qYt/5XKmVWS8
JwTvuKKCZ/95JRMk0ZMRueQduH7tSijZ
=MefQ
@


1.55
log
@See ChangeLog: Thu Sep  2 16:40:55 CEST 1999  Werner Koch
@
text
@d5 1
a5 1
			   Version 0.9.11
d7 2
a8 2
    GnuPG is a tool for secure communication and data storage.	It
    can be used to encrypt data and to create digital signatures.
d10 1
a10 1
    to the proposed OpenPGP Internet standard as described in RFC2440.
d12 4
a15 8
    GnuPG is now in Beta test and you should report all bugs to the
    mailing list (see below).  The 0.9.x versions are released mainly
    to fix all remaining serious bugs.	As soon as version 1.0 is out,
    development will continue with a 1.1 series and bug fixes for the
    1.0 version as needed.

    GnuPG works best on GNU/Linux or *BSD.  Other Unices are
    also supported but are not as well tested as the Free Unices.
d31 1
a31 1
    Digest algorithms available are MD5, RIPEMD160, SHA1, and TIGER/192.
d57 3
a59 3
       binary named "gpgm"; you should install a symbolic link
       from gpgm to gpg:
	"cd /usr/local/bin; ln -s gpg gpgm"
d126 1
a126 1
       This should yield an output similar to this:
a133 2
    Introduction
    ------------
d135 9
a143 2
    A draft version of the manual is included in the subdirectory doc
    and some HOWTO documents are available online; dor a listing see:
d147 7
d156 2
a157 2
    cryptography.  GnuPG is only a tool, secure results require that YOU
    KNOW WHAT YOU ARE DOING.
d470 2
a471 29
    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GnuPG is able to look at the
    inner structure of a encrypted packet.  This command should list all
    kinds of rfc2440 messages.

	gpg --list-trustdb

    List the contents of the trust DB in a human readable format

	gpg --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpg --list-trust-path  username

    List the possible trust paths for the given username. The length
    of such a trust path is limited by the option --max-cert-depth
    which defaults to 5.

    For more options/commands see the man page or use "gpg --help".


    Other Notes
    -----------
d473 1
a474 1
    The primary WWW page is "http://www.gnupg.org"
d477 2
a478 1
    and use them if possible.
d500 1
d502 4
a505 3
    one of the pgp newsgroups to give me more time to improve
    GnuPG.  Commercial support for GnuPG is also available; please
    see the GNU service directory or search other resources.
d507 2
a508 1
    Have fun and remember: Echelon is looking at you kid.
d511 1
a511 1
Version: GnuPG v0.9.10 (GNU/Linux)
d514 4
a517 4
iQB1AwUBN86L1h0Z9MEMmFelAQFQlQL/S5jDPpDFI3wDG/soA/qMTR79YX1IXDz9
Izin49GkPHElRCoNbT3r3+T6V+lNtrZpah6JBR30//yo1OGUyoJ88yn3KC0JdtUq
NgJzX3yYUXD+Ojer+WHEL+O8D8qkZrAX
=wiUu
@


1.54
log
@See ChangeLog: Tue Aug 31 17:20:44 CEST 1999  Werner Koch
@
text
@d5 6
a10 1
			   Version 0.9.10
a22 3
    GnuPG is in compliance with RFC2440 (OpenPGP), see doc/OpenPGP for
    details.

d33 1
a33 1
    yet create Twofish encrypted messages because there no agreement
a137 1

d141 7
a147 2
    This is a brief overview how to use GnuPG - it is strongly suggested
    that you read the manual^H^H^H more information about the use of
d519 1
a519 1
    one of the pgp newsgroups and give me more time to improve
a524 1
- -----END PGP SIGNATURE-----
d526 1
a526 1
Version: GnuPG v0.9.9 (GNU/Linux)
d529 4
a532 4
iQB1AwUBN6figR0Z9MEMmFelAQHydwL+LuKC3W6kRkm0clwab3v8I7zlX0bagxzA
RStlHXdO6ln1Mo3s3nBuCfrS6LogiUgNRFhNJQ5+rjrTydz00nzcorbyTalqvMlq
Gnsu9Pd/pTPzvk6kP79yDdoBxfaQGcgw
=W8uz
@


1.53
log
@See ChangeLog: Wed Aug  4 10:34:46 CEST 1999  Werner Koch
@
text
@d32 1
a32 1
    in the OpenPG WG on how to use it together with a MDC algorithm)
d119 1
a119 1
       The finperprint of this key is published in printed form in the
d133 1
a133 1
       published via the anouncement list and probably via Usenet.
d417 1
a417 1
      All words must match excatly (not case sensitive) and appear in
d441 1
a441 1
    you can use the option "--passphrase-fd n", which works like PGPs
@


1.52
log
@See ChangeLog: Fri Jul 23 13:53:03 CEST 1999  Werner Koch
@
text
@d5 1
a5 1
			   Version 0.9.9
a14 22
    Please verify the tar file with the PGP2 or OpenPGP
    signatures provided.  My PGP2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GnuPG signatures:

    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    You may want to add this DSA key to your GnuPG pubring and use it in
    the future to verify new releases.	Because you verified this README
    file and _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be
    quite sure that the above fingerprint is correct.

    Please subscribe to announce@@gnupg.org by sending a mail with
    a subject of "subscribe" to "announce-request@@gnupg.org".  If you
    have problems, please subscribe to "gnupg-users@@gnupg.org" by sending
    mail with the subject "subscribe" to "gnupg-users-request@@gnupg.org"
    and ask there.  The gnupg.org domain is hosted in Germany to avoid
    possible legal problems (technical advices may count as a violation
    of ITAR).
d43 2
a44 1
    1)	"./configure"
d46 2
a47 1
    2) "make"
d49 1
a49 1
    3) "make install"
d51 8
a58 2
    4) You end up with a "gpg" binary in /usr/local/bin.
       Note: Because some programs rely on the existence of a
d61 1
a61 1
       $ cd /usr/local/bin; ln -s gpg gpgm
d63 1
a63 1
    5) To avoid swapping out of sensitive data, you can install "gpg" as
d68 68
d466 1
a466 1
	gpgm --list-trustdb
d470 1
a470 1
	gpgm --list-trustdb  <usernames>
d474 1
a474 1
	gpgm --list-trust-path	username
d492 17
a508 2
    To avoid possible legal problems we have decided, not to use
    the normal www.gnu.org webserver.
d519 1
d521 1
a521 1
Version: GnuPG v0.9.8a (GNU/Linux)
d524 4
a527 4
iQB1AwUBN5g4Lx0Z9MEMmFelAQE+RwL/Ws+kNklTHJnABT8YU8BqN8x310DyUm+e
ViS23npv3S/kRnHbCOOQo4cEjUYZFFrJXzQgodBvKbLVzMgdj4XQvkulTSBYK6pm
B7GeQptWRCNJ7m+Hw0Z4gwJ7giQTdfF8
=pJ7c
@


1.51
log
@See ChangeLog: Wed Jul 14 19:42:08 CEST 1999  Werner Koch
@
text
@d1 2
d5 1
a5 1
			   Version 0.9.8
d450 9
@


1.50
log
@See ChangeLog: Sat Jun 26 12:15:59 CEST 1999  Werner Koch
@
text
@a0 2
-----BEGIN PGP SIGNED MESSAGE-----

d69 1
a69 1
    4) You end up with a "gpg" binray in /usr/local/bin.
a447 9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.7 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iQB1AwUBN3SoBh0Z9MEMmFelAQE+9wL/bOTFEPvkO0drlWAu8k2P7udEzwfGlKhE
Iyr6g75FSX4NnDkHB7RjyHYvQUkc8gicxYV8pBWe5c1bMYwrpe1cMvAu+BtUfDQc
oHUbx9ln7CZ2BkEgzT5bjypugwtc6o7g
=uTFn
-----END PGP SIGNATURE-----
@


1.49
log
@See ChangeLog: Wed Jun 16 20:16:21 CEST 1999  Werner Koch
@
text
@d5 1
a5 1
			   Version 0.9.7
d35 2
a36 2
    possible legal problems with gnu.org (technical advices may count
    as a violation of ITAR).
d48 1
a48 1
    The default algorithms are now DSA and ElGamal.  ElGamal for signing
d52 3
a54 1
    algorithms are: 3DES, Blowfish, and CAST5 (Twofish will come soon).
d441 3
a443 4
    Please direct bug reports to <gnupg-bugs@@gnu.org> or, better,
    post them to the mailing list <gnupg-devel@@gnupg.org> (this is a
    closed list - subscribe before posting, see above (~line 33)).
    Please direct questions about GnuPG to the mailing list or
d454 4
a457 4
iQB1AwUBN1UgTx0Z9MEMmFelAQH93wMAt2JYGXSkJR9+VBeLlpKdjxoIylrlDWEL
Jk5U/tuuM8H8G4ZJi7lDEhJNX77Jbh2LI18eCJJdrmWPrmDCNK2udDwcyKV4nW3k
7Fzpc/j8fKJcICP+T9YU9wa0NJrrTg1v
=dgdp
@


1.48
log
@See ChangeLog: Wed Jun  2 14:17:19 CEST 1999  Werner Koch
@
text
@d3 3
a5 3
                    GnuPG - The GNU Privacy Guard
                   -------------------------------
                           Version 0.9.7
d9 1
a9 1
    to fix all remaining serious bugs.  As soon as version 1.0 is out,
d26 1
a26 1
    the future to verify new releases.  Because you verified this README
d63 1
a63 1
    1)  "./configure"
d95 1
a95 1
        gpg --gen-key
d122 1
a122 1
        gpg --gen-revoke your_user_id
d130 1
a130 1
        gpg -s file
d135 1
a135 1
        gpg -sa file
d138 1
a138 1
    and and ready for sending by mail.  It is better to use your
d143 1
a143 1
        gpg -s -o out file
d152 1
a152 1
        gpg --verify file
d163 1
a163 1
        cat signed-file | gpg | wc -l
d170 1
a170 1
        gpg -e -r heine file
d175 1
a175 1
        echo "hello" | gpg -ea -r heine | mail heine
d180 1
a180 1
        gpg -se -r heine file
d185 1
a185 1
        gpg -se -r heine -u Suttner file
d193 1
a193 1
        gpg --export >all-my-keys
d204 1
a204 1
        gpg --export --armor | mail panther@@tiger.int
d211 1
a211 1
        gpg --import [filenames]
d225 1
a225 1
        gpg --fingerprint <username>
d240 1
a240 1
    may now act as introducers to you.  Introducers signing keys thereby
d247 6
a252 6
        1. First check that there is a complete chain
           of signed keys from the public key you want to use
           and your key and verify each signature.
        2. Make sure that you have full trust in the certificates
           of all the introduces between the public key holder and
           you.
d257 1
a257 1
    needed to check the chain of certificates.  You may choose from:
d259 3
a261 3
         of the chains of certificates, in which this key is used
         as an introducer, to validate the target key.  Use this if
         you don't know the introducer.
d263 4
a266 4
         does not do a good job in certifying other keys.  The effect
         is the same as with a) but for a) you may later want to
         change the value because you got new information about this
         introducer.
d268 3
a270 3
         introducer knows what he is doing.  Together with some
         other marginally trusted keys, GnuPG validates the target
         key then as good.
d272 5
a276 5
         introducer does a good job when certifying other keys.
         If all the introducer are of this trust value, GnuPG
         normally needs only one chain of signatures to validate
         a target key okay. (But this may be adjusted with the help
         of some options).
d289 1
a289 1
        gpg --edit-key <keyid or username>
d329 4
a332 4
        "234567C4"
        "0F34E556E"
        "01347A56A"
        "0xAB123456
d336 4
a339 4
        "234AABBCC34567C4"
        "0F323456784E56EAB"
        "01AB3FED1347A5612"
        "0x234AABBCC34567C4"
d343 3
a345 3
        "1234343434343434C434343434343434"
        "123434343434343C3434343434343734349A3434"
        "0E12343434343434343434EAB3484343434343434"
d351 1
a351 1
        "=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"
d355 1
a355 1
        "<heinrichh@@uni-duesseldorf.de>"
d359 1
a359 1
        "+Heinrich Heine duesseldorf"
d367 1
a367 1
        "#34"
d374 2
a375 2
        "Heine"
        "*Heine"
d403 1
a403 1
        gpg --list-packets datafile
d410 1
a410 1
        gpgm --list-trustdb
d414 1
a414 1
        gpgm --list-trustdb  <usernames>
d418 1
a418 1
        gpgm --list-trust-path  username
d440 1
a440 1
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a
@


1.47
log
@See ChangeLog: Thu May  6 14:18:17 CEST 1999  Werner Koch
@
text
@d3 3
a5 3
		    GnuPG - The GNU Privacy Guard
		   -------------------------------
			   Version 0.9.6
d9 1
a9 1
    to fix all remaining serious bugs.	As soon as version 1.0 is out,
d26 1
a26 1
    the future to verify new releases.	Because you verified this README
d63 1
a63 1
    1)	"./configure"
d70 4
d95 1
a95 1
	gpg --gen-key
d122 1
a122 1
	gpg --gen-revoke your_user_id
d130 1
a130 1
	gpg -s file
d135 1
a135 1
	gpg -sa file
d138 1
a138 1
    and and ready for sending by mail.	It is better to use your
d143 1
a143 1
	gpg -s -o out file
d152 1
a152 1
	gpg --verify file
d163 1
a163 1
	cat signed-file | gpg | wc -l
d170 1
a170 1
	gpg -e -r heine file
d175 1
a175 1
	echo "hello" | gpg -ea -r heine | mail heine
d180 1
a180 1
	gpg -se -r heine file
d185 1
a185 1
	gpg -se -r heine -u Suttner file
d193 1
a193 1
	gpg --export >all-my-keys
d204 1
a204 1
	gpg --export --armor | mail panther@@tiger.int
d211 1
a211 1
	gpg --import [filenames]
d225 1
a225 1
	gpg --fingerprint <username>
d240 1
a240 1
    may now act as introducers to you.	Introducers signing keys thereby
d247 6
a252 6
	1. First check that there is a complete chain
	   of signed keys from the public key you want to use
	   and your key and verify each signature.
	2. Make sure that you have full trust in the certificates
	   of all the introduces between the public key holder and
	   you.
d257 1
a257 1
    needed to check the chain of certificates.	You may choose from:
d259 3
a261 3
	 of the chains of certificates, in which this key is used
	 as an introducer, to validate the target key.	Use this if
	 you don't know the introducer.
d263 4
a266 4
	 does not do a good job in certifying other keys.  The effect
	 is the same as with a) but for a) you may later want to
	 change the value because you got new information about this
	 introducer.
d268 3
a270 3
	 introducer knows what he is doing.  Together with some
	 other marginally trusted keys, GnuPG validates the target
	 key then as good.
d272 5
a276 5
	 introducer does a good job when certifying other keys.
	 If all the introducer are of this trust value, GnuPG
	 normally needs only one chain of signatures to validate
	 a target key okay. (But this may be adjusted with the help
	 of some options).
d289 1
a289 1
	gpg --edit-key <keyid or username>
d329 4
a332 4
	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456
d336 4
a339 4
	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"
d343 3
a345 3
	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"
d351 1
a351 1
	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"
d355 1
a355 1
	"<heinrichh@@uni-duesseldorf.de>"
d359 1
a359 1
	"+Heinrich Heine duesseldorf"
d367 1
a367 1
	"#34"
d374 2
a375 2
	"Heine"
	"*Heine"
d403 1
a403 1
	gpg --list-packets datafile
d410 1
a410 1
	gpgm --list-trustdb
d414 1
a414 1
	gpgm --list-trustdb  <usernames>
d418 1
a418 1
	gpgm --list-trust-path	username
d436 3
d444 2
a445 1
    GnuPG.  Commercial support for GnuPG will be available soon.
d450 1
a450 1
Version: GnuPG v0.9.5 (GNU/Linux)
d453 4
a456 4
iQB1AwUBNzFgoB0Z9MEMmFelAQG1EgL/UlmBc7X9UoSh0ge1FNSNncHQGIX8wHkG
0BHOkcHS9XNxZokgkxoUTSRDFlXxW9auWpYKYeNkkck8S9ExtOJK6FABme6Daof0
Hfe4E7TA82T73gvsMMlN6wyys3k5gTRt
=FP1e
@


1.46
log
@See ChangeLog: Fri Apr  9 12:26:25 CEST 1999  Werner Koch
@
text
@a0 5
Please note that this is only a bug fix release and some things
do not yet work - see TODO for parts which are problematic



d5 1
a5 1
			    Version 0.9
d15 1
a15 1
    Please verify the tar file with the PGP2 or GnuPG/PGP5
d21 1
d25 1
a25 5
    My new DSA key is:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may want add my new DSA key to your GnuPG pubring and use it in
d28 1
a28 1
    sure that the above fingerprints are correct.
d30 7
a36 5
    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing list is closed (only subscribers are allowed to post)
    to avoid misuse by folks who don't know the Netiquette and trash
    your mailspool with commercial junk.
d69 1
a69 1
    4) You end up with the binaries "gpg" and "gpgm" in /usr/local/bin.
d71 3
a73 1
    5) Optional, but suggested, install the binary "gpg" as suid root.
d229 2
a230 1
    card.
d442 1
a442 1
Version: GnuPG v0.9.2 (GNU/Linux)
d445 4
a448 4
iQB1AwUBNr2fPh0Z9MEMmFelAQHqNAL/e7pApR0CGUJ/zuIsjaVhNGPEgKAglcEd
YuVdB+RCN0wq7ZfI0AHU2FdVISRACmSN3xituTTgeiOUsczM40EZ4l1XNfyRF768
fglui6XxEeYHFY7mSQMgzzFWDG0Squx0
=enRo
@


1.45
log
@See ChangeLog: Sat Mar 20 12:55:33 CET 1999  Werner Koch
@
text
@a3 1
The genkey1024 test will fail due to an expect problem :-(
d8 3
a10 3
                    GnuPG - The GNU Privacy Guard
                   -------------------------------
                            Version 0.9
d14 1
a14 1
    to fix all remaining serious bugs.  As soon as version 1.0 is out,
d34 1
a34 1
    the future to verify new releases.  Because you verified this README
d69 1
a69 1
    1)  "./configure"
d95 1
a95 1
        gpg --gen-key
d122 1
a122 1
        gpg --gen-revoke your_user_id
d130 1
a130 1
        gpg -s file
d135 1
a135 1
        gpg -sa file
d138 1
a138 1
    and and ready for sending by mail.  It is better to use your
d143 1
a143 1
        gpg -s -o out file
d152 1
a152 1
        gpg --verify file
d163 1
a163 1
        cat signed-file | gpg | wc -l
d170 1
a170 1
        gpg -e -r heine file
d175 1
a175 1
        echo "hello" | gpg -ea -r heine | mail heine
d180 1
a180 1
        gpg -se -r heine file
d185 1
a185 1
        gpg -se -r heine -u Suttner file
d193 1
a193 1
        gpg --export >all-my-keys
d204 1
a204 1
        gpg --export --armor | mail panther@@tiger.int
d211 1
a211 1
        gpg --import [filenames]
d225 1
a225 1
        gpg --fingerprint <username>
d239 1
a239 1
    may now act as introducers to you.  Introducers signing keys thereby
d246 6
a251 6
        1. First check that there is a complete chain
           of signed keys from the public key you want to use
           and your key and verify each signature.
        2. Make sure that you have full trust in the certificates
           of all the introduces between the public key holder and
           you.
d256 1
a256 1
    needed to check the chain of certificates.  You may choose from:
d258 3
a260 3
         of the chains of certificates, in which this key is used
         as an introducer, to validate the target key.  Use this if
         you don't know the introducer.
d262 4
a265 4
         does not do a good job in certifying other keys.  The effect
         is the same as with a) but for a) you may later want to
         change the value because you got new information about this
         introducer.
d267 3
a269 3
         introducer knows what he is doing.  Together with some
         other marginally trusted keys, GnuPG validates the target
         key then as good.
d271 5
a275 5
         introducer does a good job when certifying other keys.
         If all the introducer are of this trust value, GnuPG
         normally needs only one chain of signatures to validate
         a target key okay. (But this may be adjusted with the help
         of some options).
d288 1
a288 1
        gpg --edit-key <keyid or username>
d328 4
a331 4
        "234567C4"
        "0F34E556E"
        "01347A56A"
        "0xAB123456
d335 4
a338 4
        "234AABBCC34567C4"
        "0F323456784E56EAB"
        "01AB3FED1347A5612"
        "0x234AABBCC34567C4"
d342 3
a344 3
        "1234343434343434C434343434343434"
        "123434343434343C3434343434343734349A3434"
        "0E12343434343434343434EAB3484343434343434"
d350 1
a350 1
        "=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"
d354 1
a354 1
        "<heinrichh@@uni-duesseldorf.de>"
d358 1
a358 1
        "+Heinrich Heine duesseldorf"
d366 1
a366 1
        "#34"
d373 2
a374 2
        "Heine"
        "*Heine"
d402 1
a402 1
        gpg --list-packets datafile
d409 1
a409 1
        gpgm --list-trustdb
d413 1
a413 1
        gpgm --list-trustdb  <usernames>
d417 1
a417 1
        gpgm --list-trust-path  username
@


1.44
log
@See ChangeLog: Mon Mar  8 20:47:17 CET 1999  Werner Koch
@
text
@d4 3
@


1.43
log
@See ChangeLog: Wed Feb 10 17:15:39 CET 1999  Werner Koch
@
text
@d1 3
@


1.42
log
@See ChangeLog: Wed Jan 13 12:49:36 CET 1999  Werner Koch
@
text
@d3 435
a437 424
		    GnuPG - The GNU Privacy Guard
		   -------------------------------
			    Version 0.9

    GnuPG is now in Beta test and you should report all bugs to the
    mailing list (see below).  The 0.9.x versions are mainly released
    to fix all remaining serious bugs.	As soon as version 1.0 is out,
    development will continue with a 1.1 series and bug fixes for the
    1.0 version are released as needed.

    GnuPG works best on GNU/Linux or *BSD.  Other Unices are
    also supported but not as good tested as those Freenix ones.
    Please verify the tar file; there is a PGP2 and a GnuPG/PGP5
    signature available. My PGP2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GnuPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    My new DSA key is:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may want add it to your GnuPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing list is a closed one (only subscribers are allowed
    to post) to avoid misuse by folks who don't know the Netiquette
    and trash your mailspool with commercial junk.

    See the file COPYING for copyright and warranty information.

    GnuPG is in compliance with RFC2440 (OpenPGP), see doc/OpenPGP for
    details.

    Due to the fact that GnuPG does not use use any patented algorithm,
    it cannot be compatible with PGP2 versions; PGP 2.x does only use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    The default algorithms are now DSA and ElGamal.  ElGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GnuPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: 3DES,
    Blowfish and CAST5 (Twofish will come soon),  available digest
    algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.


    Installation
    ------------

    Please read the file INSTALL!

    Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with the binaries "gpg" and "gpgm" in /usr/local/bin.

    5) Optional, but suggested: install the binary "gpg" as suid root.



    Intro
    -----
    This is a brief overview how to use GnuPG - it is highly suggested
    that you read the manual^H^H^H more information about the use
    of cryptography.  GnuPG is only the technical tool to do it and
    the security highly depends on that YOU KNOW WHAT YOU ARE DOING.

    If you already have a DSA key from PGP 5 (they call them DH/ElGamal)
    you can simply copy the pgp keyrings over the GnuPG keyrings after
    running gpg once, so that it can create the correct directory.

    The normal way to create a key is:

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for the key parameters, GnuPG needs to gather
    enough noise (entropy) from your system.  If you see no progress
    during key generation you should start some other activities such
    as mouse moves or hitting on the CTRL and SHIFT keys.

    Generate a key ONLY on a machine where you have direct physical
    access - don't do it over the network or on a machine used also
    by others - especially if you have no access to the root account.

    When you are asked for a passphrase; use a good one which you can easy
    remember. Don't make the passphrase too long because you have to
    type it for every decryption or signing; but - AND THIS IS VERY
    IMPORTANT - use a good one which is not easily guessable as the
    security of the whole system relies on your secret key and the
    passphrase is used to protect this secret key in case someone was
    able to get access to your secret keyring. A good way to select
    a passphrase is to figure out a short nonsense sentence which makes
    some sense for you and modify it by inserting extra spaces, non-letters
    and changing the case of some characters - this is really easy to
    remember especially if you associate some pictures with it.

    Then you should create a revocation certificate in case someone
    gets knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    Now you can use your key to create digital signatures:

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but creates the file.asc which is ascii armored and
    and ready for sending by mail.  Note: It is better to use your
    mailers features to create signatures (The mailer uses GnuPG to do
    this) because the mailer has the ability to MIME encode such
    signatures - but this is not a security issue.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    Everyone who knows your public key (you can and should publish
    your key by putting it on a key server, a web page or in your .plan
    file) is now able to check whether you really signed this text;

	gpg --verify file

    GnuPG now checks whether the signature is valid and prints an
    appropriate message.  If the signature is good, you know at least
    that the person (or machine) has access to the secret key which
    corresponds to the published public key.
    If you run gpg without an option it will verify the signature and
    create a new file which is identical to the original file.	gpg
    can also run as a filter, so that you can pipe data to verify
    trough it:

	cat signed-file | gpg | wc -l

    will check the signature of signed-file and then display the
    number of lines in the original file.

    To send a message encrypted to someone you can use this:

	gpg -e -r heine file

    This encrypts file with the public key of the user "heine" and
    writes it to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message
    to the user with the mail address heine.

	gpg -se -r heine file

    This encrypts file with the public key of "heine" and writes it
    to "file.gpg" after signing it with your user id.

	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with your alternative user id "Suttner"


    GnuPG has some options to help you publish public keys; this is
    called "exporting" a key:

	gpg --export >all-my-keys

    exports all the keys in the keyring and writes them (in a binary format)
    to all-my-keys.  You may then mail "all-my-keys" as an MIME attachment
    to someone else or put it on an FTP server. To export only some
    user IDs, you give them as arguments on the command line.

    To mail a public key or put it on a web page you have to create
    the key in ASCII armored format:

	gpg --export --armor | mail panther@@tiger.int

    This will send all your public keys to your friend panther.

    If you have received a key from someone else you can put it
    into your public keyring; is called "importing":

	gpg --import [filenames]

    New keys are appended to your keyring and already existing
    keys are updated. Note that GnuPG does not allow keys which
    are not self-signed by the user.

    Because anyone can claim that the public key belongs to her
    we must have some way to check that the public key really belongs
    to the owner.  This can be achieved by comparing the key during
    a phone call.  Sure, it is not very easy to compare a binary file
    by reading the complete hex dump of the file - GnuPG (and nearly
    every other program used for management of cryptographic keys)
    provides other solutions:

	gpg --fingerprint <username>

    prints the so called "fingerprint" of the given username; this
    is a sequence of hex bytes (which you may have noticed in mail
    sigs or on business cards) which uniquely identify the public
    key - two different keys will always have different fingerprints.
    It is easy to compare this fingerprint by phone and I suggest
    that you print your fingerprint on the back of your business
    card.

    If you don't know the owner of the public key you are in trouble;
    but wait: A friend of you knows someone who knows someone who
    has met the owner of the public key at some computer conference.
    So all the persons between you and the public key holder may now
    act as introducer to you; this is done by signing the keys and
    thereby certifying the other keys.	If you then trust all the
    introducers to correctly sign other keys, you can be be sure that
    the other key really belongs to the one who claims so.

    There are 2 steps to validate a target key:
	1. First check that there is a complete chain
	   of signed keys from the public key you want to use
	   and your key and verify each signature.
	2. Make sure that you have full trust in the certificates
	   of all the introduces between the public key holder and
	   you.
    Step 2 is the more complicated part because there is no easy way
    for a computer to decide who is trustworthy and who is not.  GnuPG
    leaves this decision to you and will ask you for a trust value
    (here also referenced as the owner-trust of a key) for every key
    needed to check the chain of certificates.	You may choose from:
      a) "I don't know" - then it is not possible to use any
	 of the chains of certificates, in which this key is used
	 as an introducer, to validate the target key.	Use this if
	 you don't know the introducer.
      b) "I do not trust" - Use this if you know that the introducer
	 does not do a good job in certifying other keys.  The effect
	 is the same as with a) but for a) you may later want to
	 change the value because you got new information about this
	 introducer.
      c) "I trust marginally" - Use this if you assume that the
	 introducer knows what he is doing.  Together with some
	 other marginally trusted keys, GnuPG validates the target
	 key then as good.
      d) "I fully trust" - Use this if you really know that this
	 introducer does a good job when certifying other keys.
	 If all the introducer are of this trust value, GnuPG
	 normally needs only one chain of signatures to validate
	 a target key okay. (But this may be adjusted with the help
	 of some options).
    These information are confidential because they give your
    personal opinion on the trustworthy of someone else.  Therefore
    this data is not stored in the keyring but in the "trustdb"
    (~/.gnupg/trustdb.gpg).  Do not assign a high trust value just
    because the introducer is a friend of you - decide how far she
    understands all the implications of key signatures and you may
    want to tell him more about public key cryptography so you
    can later change the trust value you assigned.

    Okay, here is how GnuPG helps you in key management:  Most stuff is
    done with the --edit-key  command:

	gpg --edit-key <keyid or username>

    GnuPG displays some information about the key and then prompts
    for a command (enter "help" to see a list of commands and see
    the man page for a more detailed explanation).  To sign a key
    you select the user ID you want to sign by entering the number
    which is displayed in the leftmost column (or do nothing if the
    key has only one user ID) and then enter the command "sign" and
    follow all the prompts.  When you are ready, give the command
    "save" (or use "quit" to cancel your actions).

    If you want to sign the key with another user ID of yours, you
    must give an "-u" option on the command line together with the
    "--edit-key".

    Normally you want to sign only one user ID because GnuPG
    does only use one and this keeps the public key certificate
    small.  Because such key signatures are very important you
    should make sure that the signators of your key sign a user ID
    which is very likely to stay for a long time - choose one with an
    email address you have full control of or do not enter an email
    address at all.  In future GnuPG will have a way to tell which
    user ID is the one with an email address you prefer - because
    you have no signatures on this email address it is easy to change
    this address.  Remember: Your signators sign your public key (the
    primary one) together with one of your user IDs - so it is not possible
    to change the user ID later without voiding all the signatures.

    Tip: If you hear about a key signing party on a computer conference
    join it because this is a very convenient way to get your key
    certified (But remember that signatures have nothing to to with the
    trust you assign to a key).


    7 Ways to Specify a User ID
    --------------------------
    There are several ways to specify a user ID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string:

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

    * By the Local ID (from the trust DB):

	"#34"

      This may be used by a MUA to specify an exact key after selecting
      a key from GnuPG (by the use of a special option or an extra utility)

    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.


    Batch mode
    ----------
    If you use the option "--batch", GnuPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passphrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GnuPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GnuPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or better the output of the fd specified with --status-fd to get
    detailed information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GnuPG is able to look at the
    inner structure of a encrypted packet.  This command should be able
    to list all kinds of rfc2440 messages.

	gpgm --list-trustdb

    List the contents of the trust DB in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	username

    List the possible trust paths for the given username. The length
    of such a trust path is limited by the option --max-cert-depth
    which defaults to 5.

    For more options/commands see the man page or use "gpg --help".


    Other Notes
    -----------

    The primary FTP site is "ftp://ftp.gnupg.org/pub/gcrypt/"
    The primary WWW page is "http://www.gnupg.org"

    See http://www.gnupg.org/mirrors.html for a list of FTP mirrors
    and use them if possible.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a
    closed list - subscribe before posting, see above (~line 33)).
    Please direct questions about GnuPG to the mailing list or
    one of the pgp newsgroups; this gives me more time to improve
    GnuPG.  Commercial support for GnuPG will be available soon.

    Have fun and remember: Echelon is looking at you kid.

d440 1
a440 1
Version: GnuPG v0.9.1 (GNU/Linux)
d443 4
a446 4
iQB1AwUBNpyIDR0Z9MEMmFelAQGn4gL+IVlEye5I6LplxdUExsrHQpLV21H0UXFa
/Dl1T/HjrGHj41NeW2evO4Ck2K6Z0TG5jPg9CuJdcJp0siJ8odO7BTLaF3r6gwxF
CA4EXgqhSyE8PXRPS4m4M5I7Ru/bsZrF
=HfE0
@


1.41
log
@See ChangeLog: Tue Jan 12 11:17:18 CET 1999  Werner Koch
@
text
@d427 1
d429 2
a430 2
Version: GnuPG v0.4.5 (GNU/Linux)
Comment: For info finger gcrypt@@ftp.guug.de
d432 4
a435 4
iQB1AwUBNoD99h0Z9MEMmFelAQEuQwMAgfNPPUByoNlp0qGimiHADZE+8E15rmwq
RhVhH63pEgMsPvazd01cMM9EwJyD80jjOrdZo1fyE2270NU4AjSlNsEkQ0pNZYg+
N4GL70jrOtIvclVhcsQye8J53a/fzJe7
=5+Dt
@


1.40
log
@See ChangeLog: Wed Dec 23 17:12:24 CET 1998  Werner Koch
@
text
@d37 1
a37 1
    and trash you mailspool with commercial junk.
d304 1
a304 1
    primary one) together with one od your user IDs - so it is not possible
d415 1
a415 1
    See http://www.gnugp.org/mirrors.html for a list of FTP mirrors
d423 1
a423 1
    GnuPG.  Commercial support for GnuPG will be availabe soon.
@


1.39
log
@See ChangeLog: Wed Dec 23 13:34:22 CET 1998  Werner Koch
@
text
@d1 1
a1 423
		    GnuPG - The GNU Privacy Guard
		   -------------------------------
			    Version 0.9

    GnuPG is now in Beta test and you should report all bugs to the
    mailing list (see below).  The 0.9.x versions are mainly released
    to fix all remaining serious bugs.	As soon as version 1.0 is out,
    development will continue with a 1.1 series and bug fixes for the
    1.0 version are released as needed.

    GnuPG works best on GNU/Linux or *BSD.  Other Unices are
    also supported but not as good tested as those Freenix ones.
    Please verify the tar file; there is a PGP2 and a GnuPG/PGP5
    signature available. My PGP2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GnuPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    My new DSA key is:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may want add it to your GnuPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing list is a closed one (only subscribers are allowed
    to post) to avoid misuse by folks who don't know the Netiquette
    and trash you mailspool with commercial junk.

    See the file COPYING for copyright and warranty information.

    GnuPG is in compliance with RFC2440 (OpenPGP), see doc/OpenPGP for
    details.

    Due to the fact that GnuPG does not use use any patented algorithm,
    it cannot be compatible with PGP2 versions; PGP 2.x does only use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    The default algorithms are now DSA and ElGamal.  ElGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GnuPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: 3DES,
    Blowfish and CAST5 (Twofish will come soon),  available digest
    algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.


    Installation
    ------------

    Please read the file INSTALL!

    Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with the binaries "gpg" and "gpgm" in /usr/local/bin.

    5) Optional, but suggested: install the binary "gpg" as suid root.



    Intro
    -----
    This is a brief overview how to use GnuPG - it is highly suggested
    that you read the manual^H^H^H more information about the use
    of cryptography.  GnuPG is only the technical tool to do it and
    the security highly depends on that YOU KNOW WHAT YOU ARE DOING.

    If you already have a DSA key from PGP 5 (they call them DH/ElGamal)
    you can simply copy the pgp keyrings over the GnuPG keyrings after
    running gpg once, so that it can create the correct directory.

    The normal way to create a key is:

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for the key parameters, GnuPG needs to gather
    enough noise (entropy) from your system.  If you see no progress
    during key generation you should start some other activities such
    as mouse moves or hitting on the CTRL and SHIFT keys.

    Generate a key ONLY on a machine where you have direct physical
    access - don't do it over the network or on a machine used also
    by others - especially if you have no access to the root account.

    When you are asked for a passphrase; use a good one which you can easy
    remember. Don't make the passphrase too long because you have to
    type it for every decryption or signing; but - AND THIS IS VERY
    IMPORTANT - use a good one which is not easily guessable as the
    security of the whole system relies on your secret key and the
    passphrase is used to protect this secret key in case someone was
    able to get access to your secret keyring. A good way to select
    a passphrase is to figure out a short nonsense sentence which makes
    some sense for you and modify it by inserting extra spaces, non-letters
    and changing the case of some characters - this is really easy to
    remember especially if you associate some pictures with it.

    Then you should create a revocation certificate in case someone
    gets knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    Now you can use your key to create digital signatures:

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but creates the file.asc which is ascii armored and
    and ready for sending by mail.  Note: It is better to use your
    mailers features to create signatures (The mailer uses GnuPG to do
    this) because the mailer has the ability to MIME encode such
    signatures - but this is not a security issue.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    Everyone who knows your public key (you can and should publish
    your key by putting it on a key server, a web page or in your .plan
    file) is now able to check whether you really signed this text;

	gpg --verify file

    GnuPG now checks whether the signature is valid and prints an
    appropriate message.  If the signature is good, you know at least
    that the person (or machine) has access to the secret key which
    corresponds to the published public key.
    If you run gpg without an option it will verify the signature and
    create a new file which is identical to the original file.	gpg
    can also run as a filter, so that you can pipe data to verify
    trough it:

	cat signed-file | gpg | wc -l

    will check the signature of signed-file and then display the
    number of lines in the original file.

    To send a message encrypted to someone you can use this:

	gpg -e -r heine file

    This encrypts file with the public key of the user "heine" and
    writes it to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message
    to the user with the mail address heine.

	gpg -se -r heine file

    This encrypts file with the public key of "heine" and writes it
    to "file.gpg" after signing it with your user id.

	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with your alternative user id "Suttner"


    GnuPG has some options to help you publish public keys; this is
    called "exporting" a key:

	gpg --export >all-my-keys

    exports all the keys in the keyring and writes them (in a binary format)
    to all-my-keys.  You may then mail "all-my-keys" as an MIME attachment
    to someone else or put it on an FTP server. To export only some
    user IDs, you give them as arguments on the command line.

    To mail a public key or put it on a web page you have to create
    the key in ASCII armored format:

	gpg --export --armor | mail panther@@tiger.int

    This will send all your public keys to your friend panther.

    If you have received a key from someone else you can put it
    into your public keyring; is called "importing":

	gpg --import [filenames]

    New keys are appended to your keyring and already existing
    keys are updated. Note that GnuPG does not allow keys which
    are not self-signed by the user.

    Because anyone can claim that the public key belongs to her
    we must have some way to check that the public key really belongs
    to the owner.  This can be achieved by comparing the key during
    a phone call.  Sure, it is not very easy to compare a binary file
    by reading the complete hex dump of the file - GnuPG (and nearly
    every other program used for management of cryptographic keys)
    provides other solutions:

	gpg --fingerprint <username>

    prints the so called "fingerprint" of the given username; this
    is a sequence of hex bytes (which you may have noticed in mail
    sigs or on business cards) which uniquely identify the public
    key - two different keys will always have different fingerprints.
    It is easy to compare this fingerprint by phone and I suggest
    that you print your fingerprint on the back of your business
    card.

    If you don't know the owner of the public key you are in trouble;
    but wait: A friend of you knows someone who knows someone who
    has met the owner of the public key at some computer conference.
    So all the persons between you and the public key holder may now
    act as introducer to you; this is done by signing the keys and
    thereby certifying the other keys.	If you then trust all the
    introducers to correctly sign other keys, you can be be sure that
    the other key really belongs to the one who claims so.

    There are 2 steps to validate a target key:
	1. First check that there is a complete chain
	   of signed keys from the public key you want to use
	   and your key and verify each signature.
	2. Make sure that you have full trust in the certificates
	   of all the introduces between the public key holder and
	   you.
    Step 2 is the more complicated part because there is no easy way
    for a computer to decide who is trustworthy and who is not.  GnuPG
    leaves this decision to you and will ask you for a trust value
    (here also referenced as the owner-trust of a key) for every key
    needed to check the chain of certificates.	You may choose from:
      a) "I don't know" - then it is not possible to use any
	 of the chains of certificates, in which this key is used
	 as an introducer, to validate the target key.	Use this if
	 you don't know the introducer.
      b) "I do not trust" - Use this if you know that the introducer
	 does not do a good job in certifying other keys.  The effect
	 is the same as with a) but for a) you may later want to
	 change the value because you got new information about this
	 introducer.
      c) "I trust marginally" - Use this if you assume that the
	 introducer knows what he is doing.  Together with some
	 other marginally trusted keys, GnuPG validates the target
	 key then as good.
      d) "I fully trust" - Use this if you really know that this
	 introducer does a good job when certifying other keys.
	 If all the introducer are of this trust value, GnuPG
	 normally needs only one chain of signatures to validate
	 a target key okay. (But this may be adjusted with the help
	 of some options).
    These information are confidential because they give your
    personal opinion on the trustworthy of someone else.  Therefore
    this data is not stored in the keyring but in the "trustdb"
    (~/.gnupg/trustdb.gpg).  Do not assign a high trust value just
    because the introducer is a friend of you - decide how far she
    understands all the implications of key signatures and you may
    want to tell him more about public key cryptography so you
    can later change the trust value you assigned.

    Okay, here is how GnuPG helps you in key management:  Most stuff is
    done with the --edit-key  command:

	gpg --edit-key <keyid or username>

    GnuPG displays some information about the key and then prompts
    for a command (enter "help" to see a list of commands and see
    the man page for a more detailed explanation).  To sign a key
    you select the user ID you want to sign by entering the number
    which is displayed in the leftmost column (or do nothing if the
    key has only one user ID) and then enter the command "sign" and
    follow all the prompts.  When you are ready, give the command
    "save" (or use "quit" to cancel your actions).

    If you want to sign the key with another user ID of yours, you
    must give an "-u" option on the command line together with the
    "--edit-key".

    Normally you want to sign only one user ID because GnuPG
    does only use one and this keeps the public key certificate
    small.  Because such key signatures are very important you
    should make sure that the signators of your key sign a user ID
    which is very likely to stay for a long time - choose one with an
    email address you have full control of or do not enter an email
    address at all.  In future GnuPG will have a way to tell which
    user ID is the one with an email address you prefer - because
    you have no signatures on this email address it is easy to change
    this address.  Remember: Your signators sign your public key (the
    primary one) together with one od your user IDs - so it is not possible
    to change the user ID later without voiding all the signatures.

    Tip: If you hear about a key signing party on a computer conference
    join it because this is a very convenient way to get your key
    certified (But remember that signatures have nothing to to with the
    trust you assign to a key).


    7 Ways to Specify a User ID
    --------------------------
    There are several ways to specify a user ID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string:

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

    * By the Local ID (from the trust DB):

	"#34"

      This may be used by a MUA to specify an exact key after selecting
      a key from GnuPG (by the use of a special option or an extra utility)

    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.


    Batch mode
    ----------
    If you use the option "--batch", GnuPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passphrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GnuPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GnuPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or better the output of the fd specified with --status-fd to get
    detailed information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GnuPG is able to look at the
    inner structure of a encrypted packet.  This command should be able
    to list all kinds of rfc2440 messages.

	gpgm --list-trustdb

    List the contents of the trust DB in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	username

    List the possible trust paths for the given username. The length
    of such a trust path is limited by the option --max-cert-depth
    which defaults to 5.

    For more options/commands see the man page or use "gpg --help".


    Other Notes
    -----------

    The primary FTP site is "ftp://ftp.gnupg.org/pub/gcrypt/"
    The primary WWW page is "http://www.gnupg.org"

    See http://www.gnugp.org/mirrors.html for a list of FTP mirrors
    and use them if possible.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a
    closed list - subscribe before posting, see above (~line 33)).
    Please direct questions about GnuPG to the mailing list or
    one of the pgp newsgroups; this gives me more time to improve
    GnuPG.  Commercial support for GnuPG will be availabe soon.

    Have fun and remember: Echelon is looking at you kid.
d3 433
@


1.38
log
@See ChangeLog: Thu Dec 17 18:31:15 CET 1998  Werner Koch
@
text
@d1 14
a14 14
-----BEGIN PGP SIGNED MESSAGE-----

		  GnuPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.4

    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GnuPG
    signature available. My PGP 2 key is well known and published in
d22 1
a22 5
    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
d26 1
a26 1
    You may add it to your GnuPG pubring and use it in the future to
d33 3
a35 1
    This mailing is closed (only subscribers can post) to avoid spam.
d39 3
d43 1
a43 1
    it cannot be compatible with old PGP versions, because those use
d47 1
a47 4
    GnuPG is in compliance with RFC2440 (OpenPGP), see doc/OpenPGP for
    deatils.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
d50 3
a52 3
    signatures is *not* insecure).  Symmetric algorithms are: 3DES, Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.

d68 3
a70 1
    4) You end up with a binary "gpg" in /usr/local/bin
a71 1
    5) Optional, but suggested: install the program "gpg" as suid root.
d74 6
d81 5
a85 2
    Key Generation
    --------------
d90 20
a109 6
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.
d111 2
a112 2
    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:
d120 1
a120 30
    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----
d129 5
a133 1
    Same as above, but file.gpg is ascii armored.
d139 14
a152 2
    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).
d154 1
d156 4
a159 2
    Encrypt
    -------
d163 2
a164 2
    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"
d168 2
a169 5
    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------
d173 2
a174 2
    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.
d176 1
d178 1
a178 1
	gpg -se -r heine -u Suttner file
a179 1
    Ditto, but sign the file with the user id "Suttner"
d181 2
d184 1
a184 3
    Keyring Management
    ------------------
    To export your complete keyring(s) do this:
d186 4
a189 1
	gpg --export
d191 2
a192 1
    To export only some user ids do this:
d194 1
a194 1
	gpg --export userids
d196 1
a196 1
    Use "-a" or "--armor" to create ASCII armored output.
d198 2
a199 1
    Importing keys is done with the option, you guessed it, "--import":
d203 111
a313 7
    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:
d337 1
a337 1
    * By an exact string (not yet implemented):
d345 1
a345 4
      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):
d349 1
a349 1
      This can be used by a MUA to specify an exact key after selecting
a351 1

a359 2


d365 1
a365 1
    you can use the option "--passhrase-fd n", which works like PGPs
d376 2
a377 2
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.
d387 2
a388 1
    inner structure of a encrypted packet.
d392 1
a392 1
    List the contents of the trustdb in a human readable format
d398 1
a398 8
	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.
d400 3
a402 1
	gpgm --print-mds  filenames
d404 1
a404 22
    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff
a408 2
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.
d413 2
a414 2
    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.
d417 5
a421 2
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting, see above (~line 33)).
d423 1
a424 9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.4.4 (GNU/Linux)
Comment: For info finger gcrypt@@ftp.guug.de

iQB1AwUBNlXAUh0Z9MEMmFelAQFmhwL/RfW9WxAMTh/edDy0yGTJjDgo7d/Kfmtq
8C0LJ4b2M0py1ctW6jZyiQsYtvkrttKiTYXGtRoIzVFWX2hqABKPCTHzOeXQEOSu
ro5fnRwsuj9cRxhH8lpN+diY+m1E5Fu3
=sciv
-----END PGP SIGNATURE-----
@


1.37
log
@Ready for version 0.4.4
@
text
@d3 333
a335 333
		  GnuPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.4

    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GnuPG
    signature available. My PGP 2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GnuPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may add it to your GnuPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing is closed (only subscribers can post) to avoid spam.

    See the file COPYING for copyright and warranty information.

    Due to the fact that GnuPG does not use use any patented algorithm,
    it cannot be compatible with old PGP versions, because those use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    GnuPG is in compliance with RFC2440 (OpenPGP), see doc/OpenPGP for
    deatils.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GnuPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: 3DES, Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.



    Installation
    ------------

    Please read the file INSTALL!

    Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with a binary "gpg" in /usr/local/bin

    5) Optional, but suggested: install the program "gpg" as suid root.



    Key Generation
    --------------

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.

    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but file.gpg is ascii armored.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).


    Encrypt
    -------

	gpg -e -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------

	gpg -se -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.


	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with the user id "Suttner"


    Keyring Management
    ------------------
    To export your complete keyring(s) do this:

	gpg --export

    To export only some user ids do this:

	gpg --export userids

    Use "-a" or "--armor" to create ASCII armored output.

    Importing keys is done with the option, you guessed it, "--import":

	gpg --import [filenames]

    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string (not yet implemented):

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):

	"#34"

      This can be used by a MUA to specify an exact key after selecting
      a key from GnuPG (by the use of a special option or an extra utility)


    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.




    Batch mode
    ----------
    If you use the option "--batch", GnuPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passhrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GnuPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GnuPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GnuPG is able to look at the
    inner structure of a encrypted packet.

	gpgm --list-trustdb

    List the contents of the trustdb in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.

	gpgm --print-mds  filenames

    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff


    Other Notes
    -----------
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.

    The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
    The primary WWW page is "http://www.d.shuttle.de/isil/gnupg/"

    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting, see above (~line 33)).


@


1.36
log
@See ChangeLog ;-).  Key validation should now be faster
@
text
@d3 333
a335 333
		  GnuPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.4

    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GnuPG
    signature available. My PGP 2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GnuPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may add it to your GnuPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing is closed (only subscribers can post) to avoid spam.

    See the file COPYING for copyright and warranty information.

    Due to the fact that GnuPG does not use use any patented algorithm,
    it cannot be compatible with old PGP versions, because those use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    GnuPG is in compliance with RFC2440 (OpenPGP), see doc/OpenPGP for
    deatils.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GnuPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: 3DES, Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.



    Installation
    ------------

    Please read the file INSTALL!

    Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with a binary "gpg" in /usr/local/bin

    5) Optional, but suggested: install the program "gpg" as suid root.



    Key Generation
    --------------

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.

    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but file.gpg is ascii armored.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).


    Encrypt
    -------

	gpg -e -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------

	gpg -se -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.


	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with the user id "Suttner"


    Keyring Management
    ------------------
    To export your complete keyring(s) do this:

	gpg --export

    To export only some user ids do this:

	gpg --export userids

    Use "-a" or "--armor" to create ASCII armored output.

    Importing keys is done with the option, you guessed it, "--import":

	gpg --import [filenames]

    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string (not yet implemented):

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):

	"#34"

      This can be used by a MUA to specify an exact key after selecting
      a key from GnuPG (by the use of a special option or an extra utility)


    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.




    Batch mode
    ----------
    If you use the option "--batch", GnuPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passhrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GnuPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GnuPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GnuPG is able to look at the
    inner structure of a encrypted packet.

	gpgm --list-trustdb

    List the contents of the trustdb in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.

	gpgm --print-mds  filenames

    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff


    Other Notes
    -----------
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.

    The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
    The primary WWW page is "http://www.d.shuttle.de/isil/gnupg/"

    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting, see above (~line 33)).


d337 1
a337 1
Version: GNUPG v0.4.2 (GNU/Linux)
d340 4
a343 4
iQB1AwUBNkXLyx0Z9MEMmFelAQExuwMArLtkLI3vpxZ7tCoit6hELkpyEHe10Bo6
Ms72TXasJ8L0tKNKRE2kagV7Ie7wxl0dyENlumOxsZIKLq8DGSyjSoE7GmMQEEff
ZU+4xpO3KMw6XpJMvUWwlxpm2/WDpYTa
=Y10x
@


1.35
log
@ready to release 0.4.3
@
text
@d3 333
a335 333
		  GnuPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.4

    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GnuPG
    signature available. My PGP 2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GnuPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may add it to your GnuPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing is closed (only subscribers can post) to avoid spam.

    See the file COPYING for copyright and warranty information.

    Due to the fact that GnuPG does not use use any patented algorithm,
    it cannot be compatible with old PGP versions, because those use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    GnuPG is in almost all  aspects compatible with other OpenPGP
    implementations.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GnuPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: 3DES, Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.



    Installation
    ------------

    Please read the file INSTALL!

    Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with a binary "gpg" in /usr/local/bin

    5) Optional, but suggested: install the program "gpg" as suid root.



    Key Generation
    --------------

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.

    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but file.gpg is ascii armored.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).


    Encrypt
    -------

	gpg -e -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------

	gpg -se -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.


	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with the user id "Suttner"


    Keyring Management
    ------------------
    To export your complete keyring(s) do this:

	gpg --export

    To export only some user ids do this:

	gpg --export userids

    Use "-a" or "--armor" to create ASCII armored output.

    Importing keys is done with the option, you guessed it, "--import":

	gpg --import [filenames]

    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string (not yet implemented):

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):

	"#34"

      This can be used by a MUA to specify an exact key after selecting
      a key from GnuPG (by the use of a special option or an extra utility)


    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.




    Batch mode
    ----------
    If you use the option "--batch", GnuPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passhrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GnuPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GnuPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GnuPG is able to look at the
    inner structure of a encrypted packet.

	gpgm --list-trustdb

    List the contents of the trustdb in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.

	gpgm --print-mds  filenames

    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff


    Other Notes
    -----------
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.

    The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
    The primary WWW page is "http://www.d.shuttle.de/isil/gnupg/"

    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting, see above (~line 33)).


@


1.34
log
@Snapshot release 0.4.2
@
text
@d1 1
a1 332
		  GnuPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.4

    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GnuPG
    signature available. My PGP 2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GnuPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may add it to your GnuPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing is closed (only subscribers can post) to avoid spam.

    See the file COPYING for copyright and warranty information.

    Due to the fact that GnuPG does not use use any patented algorithm,
    it cannot be compatible with old PGP versions, because those use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    GnuPG is in almost all  aspects compatible with other OpenPGP
    implementations.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GnuPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: 3DES, Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.



    Installation
    ------------

    Please read the file INSTALL!

    Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with a binary "gpg" in /usr/local/bin

    5) Optional, but suggested: install the program "gpg" as suid root.



    Key Generation
    --------------

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.

    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but file.gpg is ascii armored.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).


    Encrypt
    -------

	gpg -e -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------

	gpg -se -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.


	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with the user id "Suttner"


    Keyring Management
    ------------------
    To export your complete keyring(s) do this:

	gpg --export

    To export only some user ids do this:

	gpg --export userids

    Use "-a" or "--armor" to create ASCII armored output.

    Importing keys is done with the option, you guessed it, "--import":

	gpg --import [filenames]

    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string (not yet implemented):

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):

	"#34"

      This can be used by a MUA to specify an exact key after selecting
      a key from GnuPG (by the use of a special option or an extra utility)


    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.




    Batch mode
    ----------
    If you use the option "--batch", GnuPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passhrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GnuPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GnuPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GnuPG is able to look at the
    inner structure of a encrypted packet.

	gpgm --list-trustdb

    List the contents of the trustdb in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.

	gpgm --print-mds  filenames

    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff


    Other Notes
    -----------
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.

    The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
    The primary WWW page is "http://www.d.shuttle.de/isil/gnupg/"

    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting, see above (~line 33)).

d3 342
@


1.33
log
@last local commit
@
text
@a333 8
    Supported targets:
    ------------------
      powerpc-unknown-linux-gnu  (linuxppc)
      hppa1.1-hp-hpux10.20




@


1.32
log
@backup
@
text
@d1 1
a1 1
		  GNUPG - The GNU Privacy Guard
d11 1
a11 1
    use it.  Please verify the tar file; there is a PGP and a GNUPG
d16 1
a16 1
    the key used to make GNUPG signatures:
d28 1
a28 1
    You may add it to your GNUPG pubring and use it in the future to
d39 1
a39 1
    Due to the fact that GNUPG does not use use any patented algorithm,
d44 1
a44 1
    GNUPG is in almost all  aspects compatible with other OpenPGP
d49 1
a49 1
    is depreciated (Please note that the GNUPG implementation of ElGamal
d233 1
a233 1
      a key from GNUPG (by the use of a special option or an extra utility)
d248 1
a248 1
    If you use the option "--batch", GNUPG runs in non-interactive mode and
d254 1
a254 1
    Batch mode also causes GNUPG to terminate as soon as a BAD signature is
d260 1
a260 1
    GNUPG returns with an exit status of 1 if in batch mode and a bad signature
d272 1
a272 1
    you are asked for the passphrase, so that GNUPG is able to look at the
@


1.31
log
@a new release
@
text
@d1 340
a340 1
-----BEGIN PGP SIGNED MESSAGE-----
a341 341
		  GNUPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.4

    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GNUPG
    signature available. My PGP 2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GNUPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may add it to your GNUPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing is closed (only subscribers can post) to avoid spam.

    See the file COPYING for copyright and warranty information.

    Due to the fact that GNUPG does not use use any patented algorithm,
    it cannot be compatible with old PGP versions, because those use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    GNUPG is in almost all  aspects compatible with other OpenPGP
    implementations.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GNUPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: 3DES, Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.



    Installation
    ------------

    Please read the file INSTALL!

    Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with a binary "gpg" in /usr/local/bin

    5) Optional, but suggested: install the program "gpg" as suid root.



    Key Generation
    --------------

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.

    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but file.gpg is ascii armored.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).


    Encrypt
    -------

	gpg -e -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------

	gpg -se -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.


	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with the user id "Suttner"


    Keyring Management
    ------------------
    To export your complete keyring(s) do this:

	gpg --export

    To export only some user ids do this:

	gpg --export userids

    Use "-a" or "--armor" to create ASCII armored output.

    Importing keys is done with the option, you guessed it, "--import":

	gpg --import [filenames]

    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string (not yet implemented):

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):

	"#34"

      This can be used by a MUA to specify an exact key after selecting
      a key from GNUPG (by the use of a special option or an extra utility)


    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.




    Batch mode
    ----------
    If you use the option "--batch", GNUPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passhrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GNUPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GNUPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GNUPG is able to look at the
    inner structure of a encrypted packet.

	gpgm --list-trustdb

    List the contents of the trustdb in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.

	gpgm --print-mds  filenames

    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff


    Other Notes
    -----------
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.

    The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
    The primary WWW page is "http://www.d.shuttle.de/isil/gnupg/"

    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting, see above (~line 33)).

-----BEGIN PGP SIGNATURE-----
Version: GNUPG v0.4.0a (GNU/Linux)
Comment: For info finger gcrypt@@ftp.guug.de

iQB1AwUBNhtSpB0Z9MEMmFelAQHWNQMAuPaj71rzjjtVNlYDV0MYljPFZqAK7tvmbH3i9Lti
UuvGPCpx1/ej7jwZ2LSQ61O8c/xRwV07chHa5MGmSGT4KZg5g5MejUOliMQJIJwjY5PoZAVb
6F7+hZf5Bt5Jl2J7
=6Mbb
-----END PGP SIGNATURE-----
@


1.30
log
@*** empty log message ***
@
text
@d1 1
a1 331
		  GNUPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.4

    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GNUPG
    signature available. My PGP 2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GNUPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may add it to your GNUPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing is closed (only subscribers can post) to avoid spam.

    See the file COPYING for copyright and warranty information.

    Due to the fact that GNUPG does not use use any patented algorithm,
    it cannot be compatible with old PGP versions, because those use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    GNUPG is in almost all  aspects compatible with other OpenPGP
    implementations.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GNUPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: 3DES, Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.



    Installation
    ------------

    Please read the file INSTALL.

    Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with a binary "gpg" in /usr/local/bin

    5) Optional, but suggested: install the program "gpg" as suid root.



    Key Generation
    --------------

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.

    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but file.gpg is ascii armored.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).


    Encrypt
    -------

	gpg -e -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------

	gpg -se -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.


	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with the user id "Suttner"


    Keyring Management
    ------------------
    To export your complete keyring(s) do this:

	gpg --export

    To export only some user ids do this:

	gpg --export userids

    Use "-a" or "--armor" to create ASCII armored output.

    Importing keys is done with the option, you guessed it, "--import":

	gpg --import [filenames]

    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string (not yet implemented):

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):

	"#34"

      This can be used by a MUA to specify an exact key after selecting
      a key from GNUPG (by the use of a special option or an extra utility)


    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.




    Batch mode
    ----------
    If you use the option "--batch", GNUPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passhrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GNUPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GNUPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GNUPG is able to look at the
    inner structure of a encrypted packet.

	gpgm --list-trustdb

    List the contents of the trustdb in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.

	gpgm --print-mds  filenames

    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff


    Other Notes
    -----------
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.

    The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
    The primary WWW page is "http://www.d.shuttle.de/isil/gnupg/"

    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting).
d3 341
@


1.29
log
@.
@
text
@d1 331
a331 1
-----BEGIN PGP SIGNED MESSAGE-----
a332 339
		  GNUPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.4

    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GNUPG
    signature available. My PGP 2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GNUPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may add it to your GNUPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing is closed (only subscribers can post) to avoid spam.

    See the file COPYING for copyright and warranty information.

    Due to the fact that GNUPG does not use use any patented algorithm,
    it cannot be compatible with old PGP versions, because those use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    GNUPG is in almost all  aspects compatible with other OpenPGP
    implementations.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GNUPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.



    Installation
    ------------

    See the file INSTALL.  Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with a binary "gpg" in /usr/local/bin

    5) Optional, but suggested: install the program "gpg" as suid root.



    Key Generation
    --------------

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.

    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but file.gpg is ascii armored.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).


    Encrypt
    -------

	gpg -e -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------

	gpg -se -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.


	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with the user id "Suttner"


    Keyring Management
    ------------------
    To export your complete keyring(s) do this:

	gpg --export

    To export only some user ids do this:

	gpg --export userids

    Use "-a" or "--armor" to create ASCII armored output.

    Importing keys is done with the option, you guessed it, "--import":

	gpg --import [filenames]

    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string (not yet implemented):

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):

	"#34"

      This can be used by a MUA to specify an exact key after selecting
      a key from GNUPG (by the use of a special option or an extra utility)


    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.




    Batch mode
    ----------
    If you use the option "--batch", GNUPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passhrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GNUPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GNUPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GNUPG is able to look at the
    inner structure of a encrypted packet.

	gpgm --list-trustdb

    List the contents of the trustdb in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.

	gpgm --print-mds  filenames

    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff


    Other Notes
    -----------
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.

    The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
    The primary WWW page is "http://www.d.shuttle.de/isil/crypt/gnupg.html"

    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting).

-----BEGIN PGP SIGNATURE-----
Version: GNUPG v0.3.5a (GNU/Linux)
Comment: Get GNUPG from ftp://ftp.guug.de/pub/gcrypt/

iQB1AwUBNgJ6bB0Z9MEMmFelAQEBHgL+JhFVCrTAK2G3NVVVQBHXU5eucNx3tQQE3UucvSBA
YaKfX8dC5QU7wfgv8nFBXMK2mnAcJhJzBT6mZwxpzTZZTh7IS4qu//R9Vgy3A06ZddxKFf2M
YFelmgdpqTL6ntJC
=JZ3m
-----END PGP SIGNATURE-----
@


1.28
log
@rel 0.3.3
@
text
@d5 1
a5 6
			  Version 0.3

    WARNING: IF YOU ARE ALREADY USING GNUPG YOU SHOULD NOW MAKE A BACKUP
    OF "gpg" BECAUSE YOU NEED IT TO CONVERT YOUR PASSPHRASE AND OTHER
    THINGS - SEE "NEWS"!

d334 1
a334 1
Version: GNUPG v0.3.2b (GNU/Linux)
d337 4
a340 4
iQB1AwUBNcy3yh0Z9MEMmFelAQEUXwMAg8h8GaecR1jWVwCqaWO4oGCyWgaxvi0yfQR1Y1GC
j6Hpo5Hwa3d2UAYETL3M42/M32uxe0Wh8PMgLTWTfhV9XjwxCNg3BBDm2Zb5Enpr9UEIFOdN
OCV3J4gED4jXDOtO
=oPV/
@


1.27
log
@ready for a new release
@
text
@d1 1
a1 334
		  GNUPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.3

    WARNING: IF YOU ARE ALREADY USING GNUPG YOU SHOULD NOW MAKE A BACKUP
    OF "gpg" BECAUSE YOU NEED IT TO CONVERT YOUR PASSPHRASE AND OTHER
    THINGS - SEE "NEWS"!


    As you can see from the version number, the program may have some
    bugs and some features may not work at all - please report this to
    the mailing list.

    On a Linux box (version 2.x.x, alpha or x86 CPU) it should
    work reliably.  You may create your key on such a machine and
    use it.  Please verify the tar file; there is a PGP and a GNUPG
    signature available. My PGP 2 key is well known and published in
    the "Global Trust Register for 1998", ISBN 0-9532397-0-5.

    I have included my pubring as "g10/pubring.asc", which contains
    the key used to make GNUPG signatures:
    "pub  1024D/57548DCD 1998-07-07 Werner Koch (gnupg sig) <dd9jn@@gnu.org>"
    "Key fingerprint = 6BD9 050F D8FC 941B 4341  2DCC 68B7 AB89 5754 8DCD"

    Old version of gnupg are signed with this key:
    "pub  1312G/FF3EAA0B 1998-02-09 Werner Koch <wk@@isil.d.shuttle.de>"
    "Key fingerprint = 8489 6CD0 1851 0E33 45DA  CD67 036F 11B8 FF3E AA0B"

    My usual key is now:
    "pub  1024D/621CC013 1998-07-07 Werner Koch <werner.koch@@guug.de>"
    "Key fingerprint = ECAF 7590 EB34 43B5 C7CF  3ACB 6C7E E1B8 621C C013"

    You may add it to your GNUPG pubring and use it in the future to
    verify new releases.  Because you verified this README file and
    _checked_that_it_is_really_my PGP2 key 0C9857A5, you can be sure
    that the above fingerprints are correct.

    Please subscribe to g10@@net.lut.ac.uk by sending a mail with
    the word "subscribe" in the body to "g10-request@@net.lut.ac.uk".
    This mailing is closed (only subscribers can post) to avoid spam.

    See the file COPYING for copyright and warranty information.

    Due to the fact that GNUPG does not use use any patented algorithm,
    it cannot be compatible with old PGP versions, because those use
    IDEA (which is patented worldwide) and RSA (which is patented in
    the United States until Sep 20, 2000).

    GNUPG is in almost all  aspects compatible with other OpenPGP
    implementations.

    The default algorithms are now DSA and ELGamal.  ELGamal for signing
    is still available, but due to the larger size of such signatures it
    is depreciated (Please note that the GNUPG implementation of ElGamal
    signatures is *not* insecure).  Symmetric algorithms are: Blowfish
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.



    Installation
    ------------

    See the file INSTALL.  Here is a quick summary:

    1)	"./configure"

    2) "make"

    3) "make install"

    4) You end up with a binary "gpg" in /usr/local/bin

    5) Optional, but suggested: install the program "gpg" as suid root.



    Key Generation
    --------------

	gpg --gen-key

    This asks some questions and then starts key generation. To create
    good random numbers for prime number generation, it uses a /dev/random
    which will only emit bytes if the kernel can gather enough entropy.
    If you see no progress, you should start some other activities such
    as mouse moves, "find /" or using the keyboard (in another window).
    Because we have no hardware device to generate randomness we have to
    use this method.

    You should make a revocation certificate in case someone gets
    knowledge of your secret key or you forgot your passphrase:

	gpg --gen-revoke your_user_id

    Run this command and store it away; output is always ASCII armored,
    so that you can print it and (hopefully never) re-create it if
    your electronic media fails.

    If you decided to create a DSA key, you should add an ElGamal
    for encryption:

	gpg --add-key user_id_of_your_key

    and follow the displayed instructions (select "ElGamal using v4 packets").


    You can sign a key with this command:

	gpg --sign-key Donald

    This let you sign the key of "Donald" with your default userid.

	gpg --sign-key -u Karl -u Joe Donald

    This let you sign the key of of "Donald" with the userids of "Karl"
    and "Joe".
    All existing signatures are checked; if some are invalid, a menu is
    offered to delete some of them, and then you are asked for every user
    whether you want to sign this key.

    You may remove a signature at any time using the option "--edit-sig",
    which asks for the sigs to remove.	Self-signatures are not removable.




    Sign
    ----

	gpg -s file

    This creates a file file.gpg which is compressed and has a signature
    attached.

	gpg -sa file

    Same as above, but file.gpg is ascii armored.

	gpg -s -o out file

    Creates a signature of file, but writes the output to the file "out".

    If you use the option "--rfc1991", gnupg tries to me more compatible
    to RFC1991 (pgp 2.x).


    Encrypt
    -------

	gpg -e -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg"

	echo "hallo" | gpg -ea -r heine | mail heine

    Ditto, but encrypts "hallo\n" and mails it as ascii armored message.


    Sign and Encrypt
    ----------------

	gpg -se -r heine file

    This encrypts files with the public key of "heine" and writes it
    to "file.gpg" after signing it with the default user id.


	gpg -se -r heine -u Suttner file

    Ditto, but sign the file with the user id "Suttner"


    Keyring Management
    ------------------
    To export your complete keyring(s) do this:

	gpg --export

    To export only some user ids do this:

	gpg --export userids

    Use "-a" or "--armor" to create ASCII armored output.

    Importing keys is done with the option, you guessed it, "--import":

	gpg --import [filenames]

    New keys are appended to the default keyring and already existing
    keys are merged.  Keys without a self-signature are ignored.


    How to Specify a UserID
    -----------------------
    There are several ways to specify a userID, here are some examples:

    * Only by the short keyid (prepend a zero if it begins with A..F):

	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456

    * By a complete keyid:

	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"

    * By a fingerprint:

	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"

      The first one is MD5 the others are ripemd160 or sha1.

    * By an exact string (not yet implemented):

	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"

    * By an email address:

	"<heinrichh@@uni-duesseldorf.de>"

      This can be used by a keyserver instead of a substring to
      find this key faster.

    * By the Local ID (from the trustdb):

	"#34"

      This can be used by a MUA to specify an exact key after selecting
      a key from GNUPG (by the use of a special option or an extra utility)


    * Or by the usual substring:

	"Heine"
	"*Heine"

      The '*' indicates substring search explicitly.




    Batch mode
    ----------
    If you use the option "--batch", GNUPG runs in non-interactive mode and
    never prompts for input data.  This does not even allow entering the
    passphrase; until we have a better solution (something like ssh-agent),
    you can use the option "--passhrase-fd n", which works like PGPs
    PGPPASSFD.

    Batch mode also causes GNUPG to terminate as soon as a BAD signature is
    detected.


    Exit status
    -----------
    GNUPG returns with an exit status of 1 if in batch mode and a bad signature
    has been detected or 2 or higher for all other errors.  You should parse
    stderr or the output of the fd specified with --status-fd to get detailed
    information about the errors.


    Esoteric commands
    -----------------

	gpg --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that GNUPG is able to look at the
    inner structure of a encrypted packet.

	gpgm --list-trustdb

    List the contents of the trustdb in a human readable format

	gpgm --list-trustdb  <usernames>

    List the tree of certificates for the given usernames

	gpgm --list-trust-path	depth  username

    List the possible trust paths for the given username, up to the specified
    depth.  If depth is negative, duplicate introducers are not listed,
    because those would increase the trust probability only minimally.
    (you must use the special option "--" to stop option parsing when
     using a negative number). This option may create new entries in the
    trustdb.

	gpgm --print-mds  filenames

    List all available message digest values for the fiven filenames

    For more options/commands see the file g10/OPTIONS, or use "gpg --help"


    Debug Flags
    -----------
    Use the option "--debug n" to output debug information. This option
    can be used multiple times, all values are ORed; n maybe prefixed with
    0x to use hex-values.

	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff


    Other Notes
    -----------
    This is work in progress, so you may find duplicated code fragments,
    ugly data structures, weird usage of filenames and other things.

    The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
    The primary WWW page is "http://www.d.shuttle.de/isil/crypt/gnupg.html"

    If you like, send your keys to <gnupg-keys@@isil.d.shuttle.de>; use
    "gpg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.

    Please direct bug reports to <gnupg-bugs@@gnu.org> or better
    post them to the mailing list <g10@@net.lut.ac.uk> (this is a closed list,
    please subscribe before posting).
d3 344
@


1.26
log
@intermediate check in
@
text
@d5 4
@


1.25
log
@edit-key is now complete
@
text
@d25 1
a25 1
    My standard key is now:
d45 2
a46 1
    GNUPG is in most aspects compatible with other OpenPGP implementations.
@


1.24
log
@sync
@
text
@d138 3
@


1.23
log
@Added new key infos
@
text
@d1 3
a3 6
-----BEGIN PGP SIGNED MESSAGE-----


                  GNUPG - The GNU Privacy Guard
                 -------------------------------
                          Version 0.3
d51 1
a51 1
    and CAST5,  Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.
d60 1
a60 1
    1)  "./configure"
d75 1
a75 1
        gpg --gen-key
d88 1
a88 1
        gpg --gen-revoke your_user_id
d97 1
a97 1
        gpg --add-key user_id_of_your_key
d104 1
a104 1
        gpg --sign-key Donald
d108 1
a108 1
        gpg --sign-key -u Karl -u Joe Donald
d117 1
a117 1
    which asks for the sigs to remove.  Self-signatures are not removable.
d125 1
a125 1
        gpg -s file
d130 1
a130 1
        gpg -sa file
d134 1
a134 1
        gpg -s -o out file
d142 1
a142 1
        gpg -e -r heine file
d147 1
a147 1
        echo "hallo" | gpg -ea -r heine | mail heine
d155 1
a155 1
        gpg -se -r heine file
d161 1
a161 1
        gpg -se -r heine -u Suttner file
d170 1
a170 1
        gpg --export
d174 1
a174 1
        gpg --export userids
d180 1
a180 1
        gpg --import [filenames]
d192 4
a195 4
        "234567C4"
        "0F34E556E"
        "01347A56A"
        "0xAB123456
d199 4
a202 4
        "234AABBCC34567C4"
        "0F323456784E56EAB"
        "01AB3FED1347A5612"
        "0x234AABBCC34567C4"
d206 3
a208 3
        "1234343434343434C434343434343434"
        "123434343434343C3434343434343734349A3434"
        "0E12343434343434343434EAB3484343434343434"
d214 1
a214 1
        "=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"
d218 1
a218 1
        "<heinrichh@@uni-duesseldorf.de>"
d225 1
a225 1
        "#34"
d233 2
a234 2
        "Heine"
        "*Heine"
d264 1
a264 1
        gpg --list-packets datafile
d270 1
a270 1
        gpgm --list-trustdb
d274 1
a274 1
        gpgm --list-trustdb  <usernames>
d278 1
a278 1
        gpgm --list-trust-path  depth  username
d287 1
a287 1
        gpgm --print-mds  filenames
a290 14
        gpgm --gen-prime n

    Generate and print a simple prime number of size n

        gpgm --gen-prime n q

    Generate a prime number suitable for ElGamal signatures of size n with
    a q as largest prime factor of n-1.

        gpgm --gen-prime n q 1

    Ditto, but calculate a generator too.


d300 11
a310 11
         value  used for
         -----  ----------------------------------------------
          1     packet reading/writing
          2     MPI details
          4     ciphers and primes (may reveal sensitive data)
          8     iobuf filter functions
          16    iobuf stuff
          32    memory allocation stuff
          64    caching
          128   show memory statistics at exit
          256   trust verification stuff
a327 11


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQB1AwUBNaIyMR0Z9MEMmFelAQGGFgMAm0RkKqH6DwIl3cu4ETQROprnwbl0sc21
05CQCsATs/0oQ8R2GhH1vXyHQnGw4Abg8IHqe+fADUA8cpf1ijfPzgeq+qhp7rqs
EenOw3xe8RrsrvovkCy91AtYl8zyVdC8
=IgnL
-----END PGP SIGNATURE-----
@


1.22
log
@0.3 ready
@
text
@d1 1
d3 4
a6 3
		  GNUPG - The GNU Privacy Guard
		 -------------------------------
			  Version 0.3
d16 1
a16 1
    signature available. My PGP key is well known and published in
d21 4
d28 4
d33 3
a35 2
    verify new releases.  Because you verified the tar file containing
    this file here, you can be sure that the above fingerprint is correct.
d54 1
a54 1
    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.
d63 1
a63 1
    1)	"./configure"
d78 1
a78 1
	gpg --gen-key
d91 1
a91 1
	gpg --gen-revoke your_user_id
d100 1
a100 1
	gpg --add-key user_id_of_your_key
d107 1
a107 1
	gpg --sign-key Donald
d111 1
a111 1
	gpg --sign-key -u Karl -u Joe Donald
d120 1
a120 1
    which asks for the sigs to remove.	Self-signatures are not removable.
d128 1
a128 1
	gpg -s file
d133 1
a133 1
	gpg -sa file
d137 1
a137 1
	gpg -s -o out file
d145 1
a145 1
	gpg -e -r heine file
d150 1
a150 1
	echo "hallo" | gpg -ea -r heine | mail heine
d158 1
a158 1
	gpg -se -r heine file
d164 1
a164 1
	gpg -se -r heine -u Suttner file
d173 1
a173 1
	gpg --export
d177 1
a177 1
	gpg --export userids
d183 1
a183 1
	gpg --import [filenames]
d195 4
a198 4
	"234567C4"
	"0F34E556E"
	"01347A56A"
	"0xAB123456
d202 4
a205 4
	"234AABBCC34567C4"
	"0F323456784E56EAB"
	"01AB3FED1347A5612"
	"0x234AABBCC34567C4"
d209 3
a211 3
	"1234343434343434C434343434343434"
	"123434343434343C3434343434343734349A3434"
	"0E12343434343434343434EAB3484343434343434"
d217 1
a217 1
	"=Heinrich Heine <heinrichh@@uni-duesseldorf.de>"
d221 1
a221 1
	"<heinrichh@@uni-duesseldorf.de>"
d228 1
a228 1
	"#34"
d236 2
a237 2
	"Heine"
	"*Heine"
d267 1
a267 1
	gpg --list-packets datafile
d273 1
a273 1
	gpgm --list-trustdb
d277 1
a277 1
	gpgm --list-trustdb  <usernames>
d281 1
a281 1
	gpgm --list-trust-path	depth  username
d290 1
a290 1
	gpgm --print-mds  filenames
d294 1
a294 1
	gpgm --gen-prime n
d298 1
a298 1
	gpgm --gen-prime n q
d303 1
a303 1
	gpgm --gen-prime n q 1
d317 11
a327 11
	 value	used for
	 -----	----------------------------------------------
	  1	packet reading/writing
	  2	MPI details
	  4	ciphers and primes (may reveal sensitive data)
	  8	iobuf filter functions
	  16	iobuf stuff
	  32	memory allocation stuff
	  64	caching
	  128	show memory statistics at exit
	  256	trust verification stuff
d346 10
@


1.21
log
@*** empty log message ***
@
text
@d4 1
d6 4
a9 1
    THIS IS ALPHA SOFTWARE, YOU MAY ENCOUNTER SOME BUGS.
d28 1
d35 3
a37 2
    the United States until Sep 20, 2000).  I'm sorry about this, but
    this is the world we have created (e.g. by using proprietary software).
d39 5
a43 12
    Because the OpenPGP standard is still a draft, GNUPG now interoperates
    with it and PGP 5.	The MUA Mutt will soon support GNUPG; it has a
    mode to fallback to another program if the received message has been
    created with RSA or IDEA.

    The default algorithms used by GNUPG are ElGamal for public-key
    encryption and signing; Blowfish with a 128 bit key for protecting
    the secret-key components, conventional and session encryption;
    RIPE MD-160 to create message digest.  DSA, SHA-1, CAST and TIGER are
    also implemented, but not used by default.	I decided not
    to use DSA as the default signing algorithm, because it allows only
    for 1024 bit keys and this may not be enough in a couple of years.
a322 2
    I will run "indent" over the source when making a real distribution,
    but for now I stick to my own formatting rules.
d330 3
a332 2
    Please direct bug reports to <gnupg-bugs@@isil.d.shuttle.de> or better
    post them to the mailing list <g10@@net.lut.ac.uk>.
@


1.20
log
@new release
@
text
@d33 4
a36 5
    Because the OpenPGP standard is still a draft, GNUPG is not yet
    compatible with it (or PGP 5) - but it will be.  The data structures
    used are compatible with PGP 2.x, so it can parse and list such files
    and PGP should be able to parse data created by GNUPG and complain
    about unsupported algorithms.
a77 25
    Key generation shows progress by printing different characters to
    stderr:
	     "."  Last 10 Miller-Rabin tests failed
	     "+"  Miller-Rabin test succeeded
	     "!"  Reloading the pool with fresh prime numbers
	     "^"  Checking a new value for the generator
	     "<"  Size of one factor decreased
	     ">"  Size of one factor increased

    The prime number for ElGamal is generated this way:

    1) Make a prime number q of 160, 200, 240 bits (depending on the keysize)
    2) Select the length of the other prime factors to be at least the size
       of q and calculate the number of prime factors needed
    3) Make a pool of prime numbers, each of the length determined in step 2
    4) Get a new permutation out of the pool or continue with step 3
       if we have tested all permutations.
    5) Calculate a candidate prime p = 2 * q * p[1] * ... * p[n] + 1
    6) Check that this prime has the correct length (this may change q if
       it seems not to be possible to make a prime of the desired length)
    7) Check whether this is a prime using trial divisions and the
       Miller-Rabin test.
    8) Continue with step 4 if we did not find a prime in step 7.
    9) Find a generator for that prime.

d86 7
@


1.19
log
@*** empty log message ***
@
text
@d5 1
a5 1
    THIS IS ALPHA SOFTWARE, YOU MAY ENCOUNTER SOOME BUGS.
@


1.18
log
@applied Mathews typo and grammar fixes
@
text
@d40 1
a40 1
    encryption and signing; Blowfish with a 160 bit key for protecting
d42 1
a42 1
    RIPE MD-160 to create message digest.  DSA, SHA-1 and CAST are
d129 1
a129 1
    which asks for the sigs to remove.  Self-signatures are not removable.
d350 1
a350 1
    "gnupg --export --armor | mail gnupg-keys@@isil.d.shuttle.de" to do this.
@


1.17
log
@new release
@
text
@d8 1
a8 1
    work reliable. You may create your key on such a machine and
d28 2
a29 2
    it cannot be compatible to old PGP versions, because those use
    IDEA (which is worldwide patented) and RSA (which is patented in
d34 2
a35 2
    compatible to it (or PGP 5) - but it will.	The data structures
    used are compatible with PGP 2.x, so it can parse an list such files
d43 3
a45 3
    also implemented, but not used on default.	I decided not
    to use DSA as default signing algorithm, because it allows only for
    1024 bit keys and this may be not enough in a couple of years.
d73 1
a73 1
    which will emit only bytes if the kernel can gather enough entropy.
d75 3
a77 3
    as mouse moves, "find /" or using the keyboard (on another window).
    Because we have no hardware device to generate random we have to use
    this method.
d81 2
a82 2
	     "."  Last 10 Miller-Rabin tests failed.
	     "+"  Miller-Rabin test succeeded.
d90 1
a90 1
    1) Make a prime number q of 160, 200, 240 bits (depending on the keysize).
d93 1
a93 1
    3) Make a pool of prime number, each of the length determined in step 2
d124 3
a126 3
    All existing signatures are checked, if some are invalid, a menu is
    offered to delete some of them, and the you are asked for every user
    wether you want to sign this key.
d129 1
a129 1
    which asks for the sigs to remove. Self-signatures are not removable.
d256 1
a256 1
    never prompts for input data.  This even does not allow to enter
d270 1
a270 1
    informations about the errors.
d294 1
a294 1
    because those would increase the trust probabilty only minimal.
d310 1
a310 1
    a q as largest primefactor of n-1.
d322 1
a322 1
    Use the option "--debug n" to output debug informations. This option
d342 1
a342 1
    ugly data structures, weird usage of filenames and other thinks.
@


1.16
log
@partial DSA support
@
text
@d5 1
a5 1
    THIS IS ALPHA SOFTWARE, EXPECT BUGS AND UNIMPLEMENTED STUFF.
a21 1

a32 1

d216 1
a216 1
    * By a fingerprint (not yet implemented):
d269 2
a270 1
    stderr to get detailed informations about the errors.
@


1.15
log
@release 0.2.9
@
text
@a5 2
    IT MAY HAPPEN THAT SOME DATA FORMATS OR PROGRAMM OPTIONS
    CHANGE WITH THE NEXT VERSION.
d106 1
a106 1
    You should make a revocation certificate in cases someone gets
d209 1
d216 1
a281 5

	gpgm --quick-random

    Do not use the stroing random generator but a faster one.  This can be
    used to generate keys for tests; those are marked as insecure.
@


1.14
log
@Renamed to GNUPG
@
text
@d85 1
a85 1
	     "."  Miller-Rabin test failed.
a88 1
	     "~"  Issued during generator checks
d206 1
a206 1
    * Only by the short keyid (prepend a zero if it start with A..F):
@


1.13
log
@import works
@
text
@d2 2
a3 2
	     G10 - The GNU Encryption and Signing Tool
	    ------------------------------------------
d11 1
a11 1
    use it.  Please verify the tar file; there is a PGP and a G10
d15 2
a16 2
    I have included my pubring as "g10/pubring.10", which contains
    the key used to make G10 signatures:
d20 1
a20 1
    You may add it to your G10 pubring and use it in the future to
d30 1
a30 1
    Due to the fact that G10 does not use use any patented algorithm,
d37 1
a37 1
    Because the OpenPGP standard is still a draft, G10 is not yet
d40 1
a40 1
    and PGP should be able to parse data created by G10 and complain
d43 1
a43 1
    The default algorithms used by G10 are ElGamal for public-key
d64 1
a64 5
    4) You end up with a binary "g10" in /usr/local/bin

    5) Optional, but suggested: install the program "g10" as suid root.

    6) Create a directory ".g10" under your home directory ("mkdir ~/.g10")
d66 1
d73 1
a73 1
	g10 --gen-key
d112 1
a112 1
	g10 --gen-revoke your_user_id
d121 1
a121 1
	g10 --sign-key Donald
d125 1
a125 1
	g10 --sign-key -u Karl -u Joe Donald
d142 1
a142 1
	g10 -s file
d144 1
a144 1
    This creates a file file.g10 which is compressed and has a signature
d147 1
a147 1
	g10 -sa file
d149 1
a149 1
    Same as above, but file.g10 is ascii armored.
d151 1
a151 1
	g10 -s -o out file
d159 1
a159 1
	g10 -e -r heine file
d162 1
a162 1
    to "file.g10"
d164 1
a164 1
	echo "hallo" | g10 -ea -r heine | mail heine
d172 1
a172 1
	g10 -se -r heine file
d175 1
a175 1
    to "file.g10" after signing it with the default user id.
d178 1
a178 1
	g10 -se -r heine -u Suttner file
d187 1
a187 1
	g10 --export
d191 1
a191 1
	g10 --export userids
d197 1
a197 1
	g10 --import [filenames]
d243 1
a243 1
      a key from G10 (by the use of a special option or an extra utility)
d258 1
a258 1
    If you use the option "--batch", G10 runs in non-interactive mode and
d264 1
a264 1
    Batch mode also causes G10 to terminate as soon as a BAD signature is
d270 1
a270 1
    G10 returns with an exit status of 1 if in batch mode and a bad signature
d278 1
a278 1
	g10 --list-packets datafile
d281 1
a281 1
    you are asked for the passphrase, so that G10 is able to look at the
d284 1
a284 1
	g10maint --quick-random
d289 1
a289 1
	g10maint --list-trustdb
d293 1
a293 1
	g10maint --list-trustdb  <usernames>
d297 1
a297 1
	g10maint --list-trust-path  depth  username
d306 1
a306 1
	g10maint --print-mds  filenames
d310 1
a310 1
	g10maint --gen-prime n
d314 1
a314 1
	g10maint --gen-prime n q
d319 1
a319 1
	g10maint --gen-prime n q 1
d324 1
a324 1
    For more options/commands see the file g10/OPTIONS, or use "g10 --help"
d354 1
a354 1
    The primary WWW page is "http://www.d.shuttle.de/isil/crypt/g10.html"
d356 2
a357 2
    If you like, send your keys to <g10-keys@@isil.d.shuttle.de>; use
    "g10 --export --armor | mail g10-keys@@isil.d.shuttle.de" to do this.
d359 1
a359 1
    Please direct bug reports to <g10-bugs@@isil.d.shuttle.de> or better
@


1.12
log
@added option export
@
text
@d112 9
d137 3
a139 1
    which asks for the sigs to remove.
d184 20
@


1.11
log
@release 0.2.3
@
text
@d5 18
a22 7

    THIS IS VERSION IS ONLY A TEST VERSION !  YOU SHOULD NOT
    USE IT FOR OTHER PURPOSES THAN EVALUATING THE CURRENT CODE.

    * The data format may change in the next version!

    * Some features are not yet implemented
d56 2
a59 4
       to enable the integrated malloc debugging stuff, use:

	"./configure --enable-m-debug"

d66 4
a69 1
    5) create a directory ".g10" under your hoem directory ("mkdir ~/.g10")
d256 1
a256 1
	--quick-random
d261 1
a261 1
	--list-trustdb
d265 1
a265 1
	--list-trustdb	<usernames>
d269 1
a269 1
	--list-trust-path  depth  username
d278 1
a278 1
	--print-mds  filenames
d282 1
a282 1
	--gen-prime n
d286 1
a286 1
	--gen-prime n q
d291 1
a291 1
	--gen-prime n q 1
d296 1
a296 1
    For more options/commands see the file g10/OPTIONS.
d326 4
a329 1
    The primary WWW page is "http://www.d.shuttle.de/isil/g10.html"
@


1.10
log
@ version 0.2.1
@
text
@a12 3
    PLEASE USE "--no-armor" BECAUSE THERE IS STILL A BUG IN IT!
    (put it into the option file)

@


1.9
log
@added initial i18n stuff
@
text
@d13 3
@


1.8
log
@Ready to test version 0.2.0
@
text
@d163 53
@


1.7
log
@Trust stuff works partly.
@
text
@a13 1
    I provide this version as a reality check to start discussion.
a16 1

a18 1

d210 2
a211 1
     using a negative number)
@


1.6
log
@started with trust stuff
@
text
@d60 1
a63 6
    Resources
    ---------
    G10 needs a directory "~/.g10" to store the default keyrings
    and other files.


d73 3
a75 2
    as mouse moves or a "find /".  Because we have no hardware device
    to generate random we have to use this method.
d108 1
a108 1
    To sign the key of of "Donald" with your default userid
d112 2
a113 1
    To sign the key of of "Donald" with the userids of "Karl" and "Joe".
d118 2
a119 2
    You may remove a signature at any time by usiing the option "--edit-sig",
    which also asks for the sigs to remove.
a165 11

    Examine a data or key file
    --------------------------

	g10 --list-packets datafile

    Use this to list the contents of a data file. If the file is encrypted
    you are asked for the passphrase, so that G10 is able to look at the
    inner structure of a encrypted packet.


d174 1
a174 1
    Batch mode also causes PGP to terminate as soon as a BAD signature is
d185 50
d252 1
a252 1

@


1.5
log
@NT version compiles
@
text
@d45 18
@


1.4
log
@added more stuff
@
text
@a8 2
    * Only some parts work.

d42 1
@


1.3
log
@very first release
@
text
@a53 1
    Create a key pair with this command:
d61 1
a61 1
    as a mouse moves or a "find /".  Because we have no hardware device
d91 19
a109 3
    Signatures
    ----------
    To create a signature, use this:
d124 3
a126 3
    Encryption
    ----------
    To encrypt data use this:
d138 45
a208 5
    Compression does not work always; this is the reason that "-z 0"
    is the default.

    This will be cleaned up of course.

a214 3
    Have fun

	Werner
@


1.2
log
@added some stuff for signing keys
@
text
@d2 1
a2 1
	     G10 - The GNU Enryption and Signing Tool
d6 1
a6 1
    THIS IS VERSION IS ONLY a TEST VERSION !  YOU SHOULD NOT
d9 2
d13 1
a13 3
    * The code to generate keys is not secure!

    * Some features are not implemented
d17 1
a17 1
    Please subscribe to g10@@net.lut.ac.uk be sending a mail with
d28 1
a28 1
    this is the world we have created (e.g. by using propiertary software).
d35 1
a35 1
    about unsupported alogorithms.
d42 1
a42 1
    to use DSA as default signing algorithm, cecause it allows only for
a44 1
    Key generation takes a long time and should be improved!
d46 110
d157 2
d160 1
d162 1
@


1.1
log
@initially checkin
@
text
@d1 50
@
