Open rsudev opened 6 years ago
@rsudev thanks for the report. can you give a hint how to create such keys, known to crash delta, with gpg?
btw. the crash seems to be around these lines: https://github.com/deltachat/deltachat-core/blob/master/libs/netpgp/src/packet-parse.c#L1290
Thanks for the fast reply :)
As I created those keys quite some years ago I frankly don't know, but gpg2 --full-generate-key
should allow you to create similar ones. I can also send you the eMail address in question via PM on IRC if you wish, so you can try my case specifically.
Some additional questions:
After replying crypted,
did you reply with an Autocrypt-enabled Enigmail, K-9 or does the reply also come from Delta with an imported secret key?
[..] the responses from delta chat where encrypted as well, but the app crashed when trying to send the response.
so the message was sent correctly and after that delta crashed?
I replied with an Autocrypt-enabled Enigmail.´ (in both cases) I entered a response in delta-chat, it was displayed with the padlock icon for the encryption and the clock icon (which should denote that it is still in sending, I guess). At what stage exactly it crashes, I don't know, but the message was seemingly not sent successfully, never reached the recipient and when re-starting delta-chat, it was tried to send it again (also crashing again). I had to reset delta-chat to break this cycle.
ok, thanks, this is very helpful.
While playing around with delta-chat I sent a message to one of my eMail accounts with an existing key. After replying crypted, the responses from delta chat where encrypted as well, but the app crashed when trying to send the response. With a different account and key, this was not an issue. The non-working account had DSA/ELG-E keys with 3072/4096 bits for signing/encryption, the working account had RSA/RSA keys with 4096/4096 bits. Could it be an issue with these types of keys? Here is the stacktrace from logcat: