GPGME_No_Matching_Secret_Key error code missing

[Marcus Brinkmann]

On Wed, Feb 12, 2003 at 12:40:46PM +0100, Marc Mutz wrote:
Content-Description: signed data
> On Wednesday 12 February 2003 01:50, Marcus Brinkmann wrote:
> <snip>
> > Please also see README-alpha.
> <snip>
> 
> The point here is that _we_ (as KMail developers) didn't start using 
> gpgme for a production-quality system. The Aegypten project introduced 
> this.

I don't know who the kmail developers are.

> To spell this out, in case it is not clear: Your code is now part of the 
> (recommended) requirements for KMail 1.5.x (note: no aegypten_branch), 
> which was just released as part of KDE 3.1.0.
> 
> I think that was the right decision, but now you have to face the fact 
> that gpgme (and pinentry, dirmanager, gpg-agent, cryptplug and gpgsm) 
> are going to be used in production environments (at least at the BSI, 
> hopefully), no matter how much you stress that it's all alpha. :-)
> 
> Apart from that, gpgme is no longer in the alpha/ subdir on your FTP 
> server...

Ingo asked:
> Or do you expect the gpgme users to show their users a list of possible
> reasons for the failure?

To spell this out, too, of course we do not expect this.  But I didn't
assume that this is what Ingo was really asking.  I think Ingo wanted to
know why there are such issues as incomplete error reporting in GPGME.  The
reason is written in README-alpha, which has nothing to do with the directory
on the FTP server listing gpgme releases.  In case you didn't look it up,
I will quote it for you in full length:

 THIS IS WORK IN PROGRESS !!!!

In particular, this means that you can not expect it to be a finished
product.  The version number 0.x should be another hint to that.  This is
good news because it means for Ingo that we have not decided that users
should live with the incorrect error reporting, but that this is something
that can be fixed as part of the progress being made.

Rhetoric questions like the one from Ingo above are silly.  Bug reports and
feature requests are not.  I am still waiting for more information on why
Ingo sees No_Passphrase where I expect Decryption_Failed or Invalid_Key.
I am also open to a discussion if a distinction between no passphrase and
bad passphrase is useful.

Thanks,
Marcus

-- 
`Rhubarb is no Egyptian god.' GNU      http://www.gnu.org    marcus@gnu.org
Marcus Brinkmann              The Hurd http://www.gnu.org/software/hurd/
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de/