Batch --verify on Windows NT

Fri Mar 30 12:29:05 2001

This is a multi-part message in MIME format.

------=_NextPart_000_00C8_01C0B914.A573D450
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
I have to automate the verification of signed (detached) documents. The =
problem is the GPG program output is quite "Informal" and difficult to =
interpret by a Windows NT application (it's informal; I think it could =
change in the next versions of GPG).
Does someone know if there's a trick to bypass the creation of a pipe =
and the parsing of the "informal" string that says "gpg: Good =
signature......." ? Is there some other way for the calling application =
to know if a detached signature is good?

Thank you very much

------=_NextPart_000_00C8_01C0B914.A573D450
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>Hi,</DIV>
<DIV>I have to automate the verification of signed (detached) documents. =
The=20
problem is the GPG program output is quite "Informal" and difficult to =
interpret=20
by a Windows NT application (it's informal; I think it could change in =
the next=20
versions of GPG).</DIV>
<DIV>Does someone know if there's a trick to bypass the creation of a =
pipe and=20
the parsing of the "informal" string that says "gpg: Good =
signature......." ? Is=20
there some other way for the calling application to know if a detached =
signature=20
is good?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thank you very much</DIV></BODY></HTML>

------=_NextPart_000_00C8_01C0B914.A573D450--