Generating GnuPG S/MINE key pair

Dan Bryant dkbryant at
Wed May 6 02:08:01 CEST 2015


On Tue, Apr 28, 2015 at 11:12 AM, Dan Bryant <dkbryant at> wrote:
> OK... I'm apparently suffering from a bad gpgsm setup.  According to
> the 2011 post (
> the following command, should just work:
>    gpgsm --gen-key | gpgsm --import
> Not for me... I get
>   gpgsm: problem looking for existing certificate: Invalid argument
>   gpgsm: error storing certificate

I found the problem.  I had a corrupt install.  I was
trying to work around problems in the 2.1.3 installer, and went about
it poorly.  I copied pinentry from gpg4win 2.2.4 (bad idea).

The better way to do it was as follows:

1) Download gnupg-w32-2.1.1_20141216.exe
2) Install {1} to %ProgramFiles(x86)%\GNU\GnuPG
3) Copy files out of {2} into %UserProfile%\GnuPG.Combined
4) Uninstall {1}
6) Stop any processes running from {2}
7) Remove directory {2}
8) Download gnupg-w32-2.1.3_20150413.exe
9) Install {8} to %ProgramFiles(x86)%\GNU\GnuPG
10) Copy files out of {9} into %UserProfile%\GnuPG.Combined
11) Stop any processes running from {9}
12) Copy %UserProfile%\GnuPG.Combined to %UserProfile%\GnuPG as Admin
13) Remove %UserProfile%\GnuPG.Combined

This will get GPA.exe and PinEntry.exe working (I hope) on a 2.1.3 baseline.

You may be able to simply install 2.1.1 then install 2.1.3 over it, I
leave others to speculate on that.  This worked for me.

The GPGSM self-sign cert now imports without error.

More information about the Gnupg-users mailing list