Internal GPG error
Neil Rossi
Rossi-n@VSAC.org
Tue Sep 10 20:14:01 2002
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C258F5.DFD2A130
Content-Type: text/plain;
charset="iso-8859-1"
Hi. We're running NT 4 and GPG 1.0.6. We have an automated process that
receives email with attachments from customers and processes the decrypted
attachments. We added the GPG capability to the existing Secret Agent
encryption last April and everything has been working nearly flawlessly.
The encryption/decryption is handled by a shelled process to the command
prompt.
In the past two weeks, however, we've gotten two errors that seem to be
internal to GPG and which cause a Dr. Watson error. The specific error is:
"Access violation (0xc0000005), Address: 0x004787d3". Because the errors
occur in the shell process, it is difficult to get specific error
information back so we could take appropriate action. (Yeah, I know, we
should try Crypto_TW and we'd be able to monitor errors, but that won't
happen until we have some resources available to code the change.)
Anyway, here's the captured command line statement and GPG's response. No
output file is created, and it generates a Dr. Watson (the painful details
are available for anyone who wants them). Other files from the same
recipient decrypt without problem most of the time. Has anyone encountered
this before? What is its likely cause?
C:\>C:\WinNT\System32\cmd.exe /C C:\WinNT\System32\gpg.exe -r"[keyname
here]" -o"C:\HOST\Dwight\test\020910084054.txt" -q --batch --no-verbose
--passphrase-fd 0 --decrypt c:\host\dwight\test\badfilepartial.gpg
<C:\HOST\dwight\test\q4s17.tmp
gpg: encrypted with 1024-bit ELG-E key, ID 98213D32, created 2002-05-21
"[keyname here]"
gpg: Problem reading source (793 bytes remaining)
gpg: handle plaintext failed: file read error
gpg: WARNING: encrypted message has been manipulated!
------_=_NextPart_001_01C258F5.DFD2A130
Content-Type: text/html;
charset="iso-8859-1"
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=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Internal GPG error</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2 FACE=3D"Arial">Hi. We're running NT 4 and GPG =
1.0.6. We have an automated process that receives email with =
attachments from customers and processes the decrypted =
attachments. We added the GPG capability to the existing Secret =
Agent encryption last April and everything has been working nearly =
flawlessly. The encryption/decryption is handled by a shelled =
process to the command prompt. </FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">In the past two weeks, however, we've =
gotten two errors that seem to be internal to GPG and which cause a Dr. =
Watson error. The specific error is: "Access violation =
(0xc0000005), Address: 0x004787d3". Because the errors occur =
in the shell process, it is difficult to get specific error information =
back so we could take appropriate action. (Yeah, I know, we =
should try Crypto_TW and we'd be able to monitor errors, but that won't =
happen until we have some resources available to code the =
change.)</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Anyway, here's the captured command =
line statement and GPG's response. No output file is created, and =
it generates a Dr. Watson (the painful details are available for anyone =
who wants them). Other files from the same recipient decrypt =
without problem most of the time. Has anyone encountered this =
before? What is its likely cause?</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Times New =
Roman">C:\>C:\WinNT\System32\cmd.exe /C C:\WinNT\System32\gpg.exe =
-r"[keyname here]" =
-o"C:\HOST\Dwight\test\020910084054.txt" -q --batch =
--no-verbose --passphrase-fd 0 --decrypt =
c:\host\dwight\test\badfilepartial.gpg =
<C:\HOST\dwight\test\q4s17.tmp</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Times New Roman">gpg: encrypted with 1024-bit =
ELG-E key, ID 98213D32, created 2002-05-21</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Times New =
Roman"> "[keyname here]"</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Times New Roman">gpg: Problem reading source =
(793 bytes remaining)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Times New Roman">gpg: handle plaintext =
failed: file read error</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Times New Roman">gpg: WARNING: encrypted =
message has been manipulated!</FONT>
</P>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C258F5.DFD2A130--