soportek soportek at lavabit.com writes:
Just before reading this I tried helping my coworker sign a local file
on her machine from the command line and we received an error something
like this:
gpg: cancelled by user
gpg: no default secret key: Operation cancelled
gpg: signing failed:
On Wed 2013-01-16 09:12:09 -0500, Patrick Brunschwig wrote:
On 15.01.13 21:10, Daniel Kahn Gillmor wrote:
Question B --
Would patches be welcome to improve the terminology around validity
and trust?
Sure, yes :-)
It's been a while, but I've finally sent a patch to the list that
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi 'soportek' (is that your name?),
OK, so I sum up. Your co-worker used her key to sign messages using Enigmail
until recently but can no longer, she receives Key not found or not valid,
and sending is aborted.
You verified that the key is
When I attempt to send a signed or signed and encypted e-mail from my
account I receive the following error.
Send operation aborted.
Key 0xABCDEF01 not found or not valid. The (sub-)key might have expired.
But my keys are not expired and they are listed and associated with my
account through the
On 01/14/2013 02:43 PM, soportek wrote:
When I attempt to send a signed or signed and encypted e-mail from my
account I receive the following error.
Send operation aborted.
Key 0xABCDEF01 not found or not valid. The (sub-)key might have expired.
i don't think this is your actual keyid.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi,
Key not found or not valid. The (sub-)key might have expired.
a key to be used for signing must either be valid, non-expired and trusted,
(which IS what you should do) [or Enigmail could be set to use non-trusted
anyway (which is meant for
