Error encrypting message

[jmesserli]

Hello,
I tried using hawkpost.co today and was experiencing the following error:

openpgp.min.0ac5ae9c7d87.js:8 Uncaught (in promise) Error: Error encrypting message: Could not find valid key packet for encryption in key 3f77ce4377661af7
    at A (https://hawkpost.co/static/javascripts/openpgp.min.0ac5ae9c7d87.js:8:29141)

This was happening here: https://hawkpost.co/box/ec362e6c-490f-42a1-9f0e-d04aa7c43378 when I clicked on the Encrypt and Send button. (The box should still be open since it Never expires.)

My GPG Key fingerprint is F3140E4A8D56FF55792112EF3F77CE4377661AF7 and I added the key using the keyserver URL https://pgp.mit.edu/pks/lookup?op=get&fingerprint=on&search=0xF3140E4A8D56FF55792112EF3F77CE4377661AF7.

I am assuming this is happening because I signed up using github, where my e-mail address is [email protected], but my public key has different e-mail adresses on it. I will probably delete the account and manually sign up with a matching e-mail address, but it might be good to inform users that their public key doesn't match their e-mail.

[dethos]

This seem to be an OpenPGP issue, but I'm not really sure. I will try to reproduce and dig into what is going on, will post the results here later. Thanks for the detailed description.

[dpflucas]

This is also happening to me. I can create boxes successfully, but when the sender tries to encrypt the message, the above error occurs.

Note that previously my account was working properly - but now this is happening with all my boxes. I didn't change any of my settings.

[dpflucas]

It looks like that, in my case, the problem was that my key was already expired. I added a new working key to my hawkpost settings, and it is working again.

Anyhow, there should be some kind of feedback in this situation - for example, do not allow the creation of boxes with expired keys.

[dethos]

@dpflucas that validation is done daily for users that provide the keyserver url (expiration and revocation), disabling the ability do create new boxes or to submit content to existing boxes. Did you provide the url or only the public key?

Probably we should expand this feature to all keys.

[dpflucas]

@dethos I provided the url

[jmesserli]

In my case, the key and all subkeys were valid when the error occurred (It expires on 2017-07-18).

[dethos]

Even after the last PR, I was able to replicate the same issue, with a key that had its expiration date extended and seems the same happened with the initial report on this issue. This has been open for too long, will add the priority tag.

[pdcribeiro]

I can't reproduce this issue. Tried using an expired and renewed key and a key for a different email address but got no errors. Tried both on the production server and on a new setup.

[pdcribeiro]

@dethos, can you help me here?

[dethos]

I cannot replicate the issue anymore as well. Since it is so old and there aren't any recent complains lets close the issue. If anything comes up we can re-open.