Re: [pgpenvelope-users] Bug/Feature report for PGPEnvelope

[L. S. <ra...@qu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 16 Feb 2000, Frank Tobin wrote:

> -----BEGIN PGPENVELOPE PROCESSED MESSAGE-----
> 
> L. Sassaman, at 00:36 on Wed, 16 Feb 2000, wrote:
> 
> > The next invocation of GnuPG will cause it to sit and wait indefinately
> > (although it gives the message "Waiting for lock file .. probably
> > dead".) I am not quoting that exactly; I will cut/paste it next time I see
> > it. When I see this, I then know I have to manually remove the lock file.
> >
> > However, this isn't visible when GnuPG is being called by PGPEnvelope.
> 
> Could you provide me information on when this occurs?  That is, is it
> during sending (encryption/signing) or receiving (decryption/verifying).
> I'm guessing verifying, because only then is GnuPG's stderr (error/logging
> output) trapped.

- From what I can tell, it occurs when gpg tries to alter the file that is
locked (either keyring or trust.db).

So basically, whenever GnuPG tries to verify sigs for which the signing
key is not on the keyring, this will occur.

This is particularily troublesome with the procmail implementation.

__

L. Sassaman

System Administrator                |  "All of the chaos
Technology Consultant               |   Makes perfect sense..."
icq.. 10735603                      |
pgp.. finger://ns.quickie.net/rabbi |              --Joe Diffie



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: OpenPGP Encrypted Email Preferred.

iD8DBQE4qkozPYrxsgmsCmoRAvbJAJ4hRXno/SMaSZygiZVCfhnt51n8fwCgtz3a
YYeShFGfIL/DYRlPfsvTxps=
=nEgb
-----END PGP SIGNATURE-----