Installing GPG on W2K

[Leigh S. Jones, KR6X]

> I didn't list the key first.  I simply create keypairs using gen-key.
Will
> that cause any problem?  Or should I always do a list key first.  I am
> setting this up on my machine for test only, eventually I have to install
it
> on the computer of the girl who has to do the encryption and decryption.
So
> any advice is appreciated.

This works fine.  No need to create the database before creating the
first keys.  Gnupg will take care of it.

> I am just not sure if
> that is all to install gpg: there is no update to registry, no change to
> path, and no information on how to install, kind of like the old DOS app.

Right.  Of course, you might have preferred to place gpg into the path.
If you use WinPT then you have to tell WinPT where gpg has been
placed ("C:\Gnupg" in your case), and if you don't use "C:\Gnupg" as
your database location, then you have to make other changes.  I'd
suggest placing a copy of gpg.exe into your C:\Winnt directory.  That
directory is always in the path.  If you do, make sure that the two files
"C:\Gnupg\gpg.exe" and "C:\Winnt\gpg.exe" are always the same --
update them at the same time.  Otherwise, add "C:\Gnupg" to the
path.  Then it will execute no matter what directory your "cmd" prompt
is in at the time.  It's OK to have multiple copies of gpg.exe on your
system if you don't try to use them at the same.

> Anywhere I can download information about  customizing the
> options?

The options file contained in the gpg 1.0.6 distribution might help.
Using 1.0.6 you will probably want some options in there.  With 1.0.7
the default options are a little bit more like what you'd want than the
1.0.6 defaults.

Second to that, you should know that the information in the options
file is described when you type "gpg --help".

There are two things that might go on the command line:

commands
options

Commands generally will need to be the last thing on the gpg
command line, such as:

gpg -d encrypted_file.asc

The command is -d, same as --decrypt, with a filename parameter.

Options are generally placed in front of the command:

gpg --armor --encrypt unsecured_file.txt > secured_file.asc

or

gpg -o secured_file.asc --armor --encrypt unsecured_file.txt

Placing options into the options file means you don't have to
type them into the command line.  If you need something
different from what the contents of your options file would
dictate, then you override the options by placing new
options on the command line:

options file:

quiet

(note: you don't put the "--" in front of the options in the
options file)

command line:

gpg --verbose -d encrypted_file.asc

Usually it's convenient to put things like local-user <name>
in your options file.

----- Original Message -----
From: "Ping Kam" <pkam@quikcard.com>
To: "Leigh S. Jones, KR6X" <kr6x@kr6x.com>
Sent: Thursday, May 09, 2002 14:31
Subject: Re: Installing GPG on W2K


> Hi, Leigh:
>
> Thanks for your reply.
>
> You were obviously just beginning to install gpg.
> I am not sure when I stand.  Like I said in my previous mail.  I created
the
> 'c:\gnupg' directory and copied the gpg.exe to my local machine (in the
> 'c:\gnupg' directory).  But when I run it as directed by the installion
> guide in the readme.w32, I was puzzled because nothing seems to happen.
So
> I read the handbook.  I have successfully created two keypairs, export a
> public key from one of them.  Import a public key from our client.
> Encrypted and signed one test file to our client.  Decrypted one test file
> from our client.  Everything seems to working okay.  I am just not sure if
> that is all to install gpg: there is no update to registry, no change to
> path, and no information on how to install, kind of like the old DOS app.
>
>
> Before I go on, I'd like to point out, in case you aren't aware of this,
> that gpg.exe for W32 is a console application only, no window appears when
> gpg is run.
> I am aware of that.  I have been working in the cmd window so far.  I just
> want to make sure I can get it to work properly in the cmd window before
> exploring any GUI.
>
>
> On Win2K you can add WinPT if you like to get a user interface.  There are
a
> few details with an installation like this -- the most important being
that
> the WinPT 5.5x release was written for GnuPG 1.0.6 and will have a few
> problems with the new trust database interface in gpg 1.0.7.  It doesn't
> prevent you from using the encrypt/decrypt/sign/verify functions, but some
> key management functions will still have to be done at the command line
with
> gpg 1.0.7.  WinPT still takes over the keyserver interface, which is a
good
> thing.
> I am now using the 1.0.6.  I don't have the need to go to 1.0.7 at this
> moment so I can wait.  I have download the GPGShell 2.83 for GPG 1.0.6 but
> it raise an exception when it starts up after the installation complains
> that 'VBxxxxx.dll' is missing from the path.  I will give the WinPT a try.
>
>
> Hit <ctrl>Z if you ever start up gpg from the command line without
> parameters and don't know what to do next.  Really, gpg wasn't intended to
> be used in an interactive mode with you typing in messages at the command
> line.  The ability that gpg has to accept input from "stdin" and put it's
> output on "stdout" is intended for use by batch programs.
> I stopped it by entering <ctrl>C after a few minutes.  I just don't know
why
> the installation guide in the readme.w32 asks me to do that.
>
>
> To begin with, type gpg --help
> This is your way to get reminders about the commands you will need to use
> gpg.
> I will give it a try.
>
>
> Your first step will be to force gpg to build a key database at
> c:\gnupg\secring.gpg etc.  To do this, you type gpg --list-keys.  You will
> get an error message.  Type gpg --list-keys again.  The key databases have
> been created.
> I didn't list the key first.  I simply create keypairs using gen-key.
Will
> that cause any problem?  Or should I always do a list key first.  I am
> setting this up on my machine for test only, eventually I have to install
it
> on the computer of the girl who has to do the encryption and decryption.
So
> any advice is appreciated.
>
>
> Next you will need to create keys or import keys into the database.  You
> might really want to customize the c:\gnupg\options file first, but this
> takes some understanding of what you are doing.  If you don't have any
keys
> to import, then perhaps you should go right ahead and create some.
> I have already created some keypairs.  But I haven't played with the
options
> file yet.  Anywhere I can download information about  customizing the
> options?
>
>
> If you know what software you want gpg to interact with, for instance PGP
> 2.63, then let us know here and we'll give you some advice on how to set
up
> your options file before you go on.  Otherwise, you may not need to put
> anything into the options file now, especially since on Win2k the
keyserver
> functions won't work.
> I couldn't think of any.  We don't have to interact with PGP, at least,
for
> the moment.  My biggest concern is whether GPG is properly installed.
>
> Again, thanks for your advise.
> Ping Kam
>
>