Need to distinguish between g10_log_info and g10_log_error

Oleg V. Zhylin ovz at
Fri Sep 26 12:16:38 CEST 2008

Yes, --skip-verify does the job, thanks. Nevertheless I will go for best practice and use the right keyring in my script.

WBR Oleg V. Zhylin   ovz at

--- On Fri, 9/26/08, Brian Candler <B.Candler at> wrote:

> From: Brian Candler <B.Candler at>
> Subject: Re: Need to distinguish between g10_log_info and g10_log_error
> To: "Oleg V. Zhylin" <ovz at>
> Cc: "Adam Milazzo" <adam at>, gnupg-devel at
> Date: Friday, September 26, 2008, 10:41 AM
> On Thu, Sep 25, 2008 at 06:06:30PM -0700, Oleg V. Zhylin
> wrote:
> >   BTW I had to overcome another problem before my
> script started functioning as it is suppsed to. The error
> message
> > 
> > gpg: Can't check signature: public key not found
> > gpg: WARNING: message was not integrity protected
> > 
> >  stably renders $?=False and I couldn't find any
> command-line settings to amend this. In my current situation
> I do have public key of the sender, it is just not at
> default $GNUPGHOME. But potentially one can run into
> situation when he doesn't have author's public key
> and its impossible to retrieve one. Still, decrypting a file
> means "success" for this person.
> Perhaps the "--skip-verify" option?


More information about the Gnupg-devel mailing list