headers
Snoken | 25 Apr 2007 10:49
Picon

No encryption


Hi,
Why can I not encrypt to the key 0xAF351431? It's locally signed by me.

Decision Hint: Sender <snoken@...> found
   Decision Hint: Recipient <per@...> found
   Decision Hint: Using profile: "Always encrypt, PGP-MIME"
   Decision Hint: Keyrule would encrypt, but preferred Encr-Key
"7911DE8BBFEE8A5D" is not valid.
   There is a newer encryption subkey 8912D145, it's marked as
"Preferred" but isn't used.

BTW Why don't I get any warning when the mail is sent unencrypted?

Snoken
Permalink | Reply | 1 comment |
headers
Kevin Coates | 25 Apr 2007 15:37

Re: No encryption


On 2007/04/25 4:49:18 AM -0400, Snoken <snoken@...> wrote:

> Why can I not encrypt to the key 0xAF351431? It's locally signed by me.

I could not repeat this. I download the above key, signed it locally and
gave it the default trust. I added it to my "Always encrypt, PGP-MIME"
rule and sent a test message to my local relay mail host so I could
intercept it to review and not send out. The successful results are below.

======
Encrypted with 4096-bit ELG-E key, ID 0x8912D145, created 3/24/2007
      "Per Tunedal <per@...>"
Encrypted with 4096-bit ELG-E key, ID 0xD6506963, created 12/7/2003
      "Kevin Coates"
Signature made 04/25/07 09:24:27
               using DSA key 0x3A8E5CAD
Good signature from "Kevin Coates"

Time: 4/25/2007 9:25:06 AM (4/25/2007 1:25:06 PM UTC)
======

Try deleting your old rule, reloading the keys, and creating a new rule.
Perhaps GPGR's old rule is currently coded to encrypt to that expired
subkey.

> BTW Why don't I get any warning when the mail is sent unencrypted?

Not sure why there was no warning.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane