Windows Version File Rename Errors -2nd Try
Joe Feenin
jfeenin@microinsight.com
Thu Jun 28 19:02:02 2001
This is a multi-part message in MIME format.
------_=_NextPart_001_01C0FFF3.E0554280
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hi!
I am working to convert my old Win32 shell for DOS based PGP
[PowerPGP] to support GPG. I have run into some errors in the Win32
version of GPG which I think may be bugs. So far I have found the same
file rename errors in the --Gen-Key function when there is already a
keyring present. I.e. when creatoing a second keypair. And also when
importing a key. =20
=20
Here is what I get when generating a second key:
=20
+++++++++++++++..+++++.++++++++++.+++++.++++++++++++++++++++++++++++++++
+++.++++
++++++++++++++++..++++++++++++++++++++..+++++.+++++++++++++++>.+++++....
........
..................+++++^^^
gpg: c:/gnupg/pubring.gpg: rename to c:/gnupg/pubring.bak failed:
Permission den
ied
gpg: can't write public key: file rename error
Key generation failed: file rename error
C:\gnupg>
=20
Note the Unix style forward slashes in the filename. Also note, I do
have permission to the files and the properties are correctly set. I
triple checked this and if I rename the old keyrings I can create new
ones fine. The rename function is failing I believe because of the
forward slashes. I thought perhaps this might just be the way it was
set to display but when I try to import a key, say Phil Zimmermans I get
the following:
=20
gpg: c:/gnupg/pubring.gpg: rename to c:/gnupg/pubring.bak failed:
Permission den
ied
gpg: error writing keyring `c:/gnupg/pubring.gpg': file rename error
gpg: key B2D7795E: public key imported
gpg: error reading `c:\gnupg\pgpkey.tmp': file rename error
gpg: import from `c:\gnupg\pgpkey.tmp' failed: file rename error
gpg: Total number processed: 0
gpg: imported: 1
=20
Here you see the incorrect slash directions in the file rename section
but the correct back slashes in the file access section where it tries
to import the tmp file. Also note that it still says it imported one
key on the last line when the import in fact failed, that too seems like
an oops. Is anyone else having this issue?
=20
Joe =20
------_=_NextPart_001_01C0FFF3.E0554280
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DWindows-1252">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4417.0">
<TITLE>Windows Version File Rename Errors -2nd Try </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2>Hi!<BR>
I am working to convert my old Win32 shell for DOS based =
PGP<BR>
[PowerPGP] to support GPG. I have run into some errors in the =
Win32<BR>
version of GPG which I think may be bugs. So far I have =
found the same<BR>
file rename errors in the --Gen-Key function when there is already a<BR>
keyring present. I.e. when creatoing a second keypair. And =
also when<BR>
importing a key. <BR>
<BR>
Here is what I get when generating a second key:<BR>
<BR>
+++++++++++++++..+++++.++++++++++.+++++.++++++++++++++++++++++++++++++++<=
BR>
+++.++++<BR>
++++++++++++++++..++++++++++++++++++++..+++++.+++++++++++++++>.+++++..=
..<BR>
........<BR>
..................+++++^^^<BR>
gpg: c:/gnupg/pubring.gpg: rename to c:/gnupg/pubring.bak failed:<BR>
Permission den<BR>
ied<BR>
gpg: can't write public key: file rename error<BR>
Key generation failed: file rename error<BR>
C:\gnupg><BR>
<BR>
Note the Unix style forward slashes in the filename. Also note, I =
do<BR>
have permission to the files and the properties are correctly set. =
I<BR>
triple checked this and if I rename the old keyrings I can create =
new<BR>
ones fine. The rename function is failing I believe because of =
the<BR>
forward slashes. I thought perhaps this might just be the way it =
was<BR>
set to display but when I try to import a key, say Phil Zimmermans I =
get<BR>
the following:<BR>
<BR>
gpg: c:/gnupg/pubring.gpg: rename to c:/gnupg/pubring.bak failed:<BR>
Permission den<BR>
ied<BR>
gpg: error writing keyring `c:/gnupg/pubring.gpg': file rename error<BR>
gpg: key B2D7795E: public key imported<BR>
gpg: error reading `c:\gnupg\pgpkey.tmp': file rename error<BR>
gpg: import from `c:\gnupg\pgpkey.tmp' failed: file rename error<BR>
gpg: Total number processed: 0<BR>
gpg: &nb=
sp; imported: 1<BR>
<BR>
Here you see the incorrect slash directions in the file rename =
section<BR>
but the correct back slashes in the file access section where it =
tries<BR>
to import the tmp file. Also note that it still says it imported =
one<BR>
key on the last line when the import in fact failed, that too seems =
like<BR>
an oops. Is anyone else having this issue?<BR>
<BR>
Joe </FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C0FFF3.E0554280--