gpg - 107
Leigh S. Jones
Thu May 2 07:14:01 2002
Thanks! I had no idea that I'd get the attention of the individual
compiled the nullify.org release through the list. I'm pleased with
opportunity you've given me to upgrade to 1.0.7 early on my WinNT
machines with the nullify release.
----- Original Message -----
From: "Keith Ray" <email@example.com>
Sent: Wednesday, May 01, 2002 8:34 PM
Subject: Re: gpg - 107
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Quoting "Leigh S. Jones, KR6X" <firstname.lastname@example.org>:
> > I'm not sure yet, but I may be seeing a slight problem with the
> > implementation from www.nullify.org. I take it to be that some of
> > operations within gpg are built to use the unix standard forward
> > where the MS backslash is required. Thus far it has only appeared
> > problem at times when other errors are being reported, such as:
> > "
> > ...
> > gpg: unable to read external program response: No error
> > gpg: Warning: unable to remove tempfile (out)
> > "d:\TEMP/gpg-4C3F2/dataout.txt":
> > No such file or directory
> > ...
> > "
> GnuPG has always used the unix forward slash, even in the Mingw32
> release. If you look at the README.W32 under "Installation
> instructions", it says, "Please use forward slashes and not the
> backslashes when setting filenames for GnuPG into the Registry."
> I compiled the binary using the latest Mingw32/CPD from CVS with the
> official source code. I also included Disastry's patch to allow
> to generate v3 RSA keys. Other than that, the binary should be
> IDENTICAL to Warner Koch's official binary.
> If you find a bug, I will be happy to apply a patch and release a
> version. Also, if anyone would like features supported that are not
> the "official" release (ie. RSA v3 Key Generation), e-mail me. My
> is to create a Win32 release that gives Windows users maximum
> flexibility with GnuPG.
> -- Keith
> -----BEGIN PGP SIGNATURE-----
> -----END PGP SIGNATURE-----
> Gnupg-users mailing list