Re: Decryption fails
On Tue, 31 May 2011 19:33:29 +0200, Felix Geller fgel...@gmail.com wrote: I get the following trace when using show --decrypt to decrypt a specific message (have to kill the process to actually get the trace): #0 0x0001006121a6 in poll () #1 0x00010006d3d2 in gpg_ctx_op_step () #2 0x00010006e5c7 in gpg_decrypt () #3 0x0001000566cf in g_mime_multipart_encrypted_decrypt () #4 0x0001a413 in show_message_part (part=0x10606fc20, #state=0x7fff5fbfd1c0, format=0x10002ef80, params=0x7fff5fbfd2c0, #first=1) at show-message.c:71 So I guess it ends up looping or waiting in poll(), but I can't tell why it would do that. I guess the next step is to post to the gmime mailing list, or? Hey, Felix. Yeah, I unfortunately don't have any other suggestions other than asking the gmime folks. Interestingly, I see the following message in your crypto test output: Error: search term did not match precisely one message. which seems to indicate that the desired message wasn't actually delivered properly, contrary to what the emacs delivery tests are stating. Not sure how that could be related, though, since it looks like the trace that you show above definitely looks like gmime caught in a poll loop. jamie. pgp4EpZBs1AvD.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: Decryption fails
On Thu, 02 Jun 2011 08:35:49 -0700, Jameson Graef Rollins
jroll...@finestructure.net wrote:
Non-text part: multipart/signed
Hey, Felix. Yeah, I unfortunately don't have any other suggestions
other than asking the gmime folks.
Jeff replied and sent me a working patch :) Not sure yet how he prefers
to publish the patch, but the problem is fixed.
Interestingly, I see the following message in your crypto test output:
Error: search term did not match precisely one message.
which seems to indicate that the desired message wasn't actually
delivered properly, contrary to what the emacs delivery tests are
stating. Not sure how that could be related, though, since it looks
like the trace that you show above definitely looks like gmime caught in
a poll loop.
Just ran the tests with a fixed poll function and it seems that many
problems remain. Don't have the time at the moment to take a closer
look, but I attached the output.
Anyway, I'm a glad decrypting user now ;)
Cheers,
Felix
jamie.
Non-text part: application/pgp-signature
crypto: Testing PGP/MIME signature verification and decryption
PASS emacs delivery of signed message
FAIL signature verification
--- crypto.2.expected 2011-06-02 16:46:27.0 +
+++ crypto.2.output 2011-06-02 16:46:27.0 +
@@ -1,23 +1 @@
-[[[{id: X,
- match: true,
- filename: Y,
- timestamp: 946728000,
- date_relative: 2000-01-01,
- tags: [inbox,signed],
- headers: {Subject: test signed message 001,
- From: Notmuch Test Suite test_su...@notmuchmail.org,
- To: test_su...@notmuchmail.org,
- Cc: ,
- Bcc: ,
- Date: 01 Jan 2000 12:00:00 -},
- body: [{id: 1,
- sigstatus: [{status: good,
- fingerprint: 5AEAB11F5E33DCE875DDB75B6D92612D94E46381,
- created: 946728000}],
- content-type: multipart/signed,
- content: [{id: 2,
- content-type: text/plain,
- content: This is a test signed message.\n},
- {id: 3,
- content-type: application/pgp-signature}]}]},
- [
+[[[{id: X,n match: true,n filename: Y,n timestamp:
946728000,n date_relative: 2000-01-01,n tags: [inbox,signed],n
headers: {Subject: test signed message 001,n From: Notmuch Test Suite
test_su...@notmuchmail.org,n To: test_su...@notmuchmail.org,n Cc: ,n
Bcc: ,n Date: 01 Jan 2000 12:00:00 -},n body: [{id: 1,n
sigstatus: [{status: good,n fingerprint:
5AEAB11F5E33DCE875DDB75B6D92612D94E46381,n created: 946728000}],n
content-type: multipart/signed,n content: [{id: 2,n content-type:
text/plain,n content: This is a test signed message.\n},n {id: 3,n
content-type: application/pgp-signature}]}]},n [
FAIL signature verification with full owner trust
--- crypto.3.expected 2011-06-02 16:46:27.0 +
+++ crypto.3.output 2011-06-02 16:46:27.0 +
@@ -1,24 +1 @@
-[[[{id: X,
- match: true,
- filename: Y,
- timestamp: 946728000,
- date_relative: 2000-01-01,
- tags: [inbox,signed],
- headers: {Subject: test signed message 001,
- From: Notmuch Test Suite test_su...@notmuchmail.org,
- To: test_su...@notmuchmail.org,
- Cc: ,
- Bcc: ,
- Date: 01 Jan 2000 12:00:00 -},
- body: [{id: 1,
- sigstatus: [{status: good,
- fingerprint: 5AEAB11F5E33DCE875DDB75B6D92612D94E46381,
- created: 946728000,
- userid: Notmuch Test Suite test_su...@notmuchmail.org
(INSECURE!)}],
- content-type: multipart/signed,
- content: [{id: 2,
- content-type: text/plain,
- content: This is a test signed message.\n},
- {id: 3,
- content-type: application/pgp-signature}]}]},
- [
+[[[{id: X,n match: true,n filename: Y,n timestamp:
946728000,n date_relative: 2000-01-01,n tags: [inbox,signed],n
headers: {Subject: test signed message 001,n From: Notmuch Test Suite
test_su...@notmuchmail.org,n To: test_su...@notmuchmail.org,n Cc: ,n
Bcc: ,n Date: 01 Jan 2000 12:00:00 -},n body: [{id: 1,n
sigstatus: [{status: good,n fingerprint:
5AEAB11F5E33DCE875DDB75B6D92612D94E46381,n created: 946728000,n userid:
Notmuch Test Suite test_su...@notmuchmail.org (INSECURE!)}],n
content-type: multipart/signed,n content: [{id: 2,n content-type:
text/plain,n content: This is a test signed message.\n},n {id: 3,n
content-type: application/pgp-signature}]}]},n [
FAIL signature verification with signer key unavailable
--- crypto.4.expected 2011-06-02 16:46:28.0 +
+++ crypto.4.output 2011-06-02 16:46:28.0 +
@@ -1,23 +1 @@
-[[[{id: X,
- match: true,
- filename: Y,
- timestamp: 946728000,
- date_relative: 2000-01-01,
- tags:
Re: Decryption fails
On Thu, 02 Jun 2011 18:49:22 +0200, Felix Geller fgel...@gmail.com wrote: Jeff replied and sent me a working patch :) Not sure yet how he prefers to publish the patch, but the problem is fixed. That's great! What did Jeff say exactly? Is the patch to gmime 2.4? Did he mention that he was including them in upstream, hopefully in the next release? Interestingly, I see the following message in your crypto test output: Error: search term did not match precisely one message. which seems to indicate that the desired message wasn't actually delivered properly, contrary to what the emacs delivery tests are stating. Not sure how that could be related, though, since it looks like the trace that you show above definitely looks like gmime caught in a poll loop. Just ran the tests with a fixed poll function and it seems that many problems remain. Don't have the time at the moment to take a closer look, but I attached the output. Those test failures look very strange to me. There are a bunch of 'n's being output after the commas in the json output. Felix, are you sure you haven't modified your source at all? jamie. pgp4mvsSQW5VC.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: Decryption fails
On Tue, 31 May 2011 00:18:26 -0700, Jameson Graef Rollins
jroll...@finestructure.net wrote:
Hey, Felix. As David said, all crypto tests should be passing with
libgmime 2.4.24. It would probably be instructive to know which crypto
tests failed and why. Maybe you could supply some output from the
failed crypto tests.
Ok, so the following tests pass:
PASS emacs delivery of signed message
PASS emacs delivery of encrypted + signed message
PASS emacs delivery of encrypted message with attachment
I'm attaching the full output for the cypto tests.
I get the following trace when using show --decrypt to decrypt a
specific message (have to kill the process to actually get the trace):
#0 0x0001006121a6 in poll ()
#1 0x00010006d3d2 in gpg_ctx_op_step ()
#2 0x00010006e5c7 in gpg_decrypt ()
#3 0x0001000566cf in g_mime_multipart_encrypted_decrypt ()
#4 0x0001a413 in show_message_part (part=0x10606fc20,
#state=0x7fff5fbfd1c0, format=0x10002ef80, params=0x7fff5fbfd2c0,
#first=1) at show-message.c:71
So I guess it ends up looping or waiting in poll(), but I can't tell why
it would do that. I guess the next step is to post to the gmime mailing
list, or?
Cheers,
Felix
crypto: Testing PGP/MIME signature verification and decryption
PASS emacs delivery of signed message
FAIL signature verification
--- crypto.2.expected 2011-05-31 17:30:47.0 +
+++ crypto.2.output 2011-05-31 17:30:47.0 +
@@ -1,23 +1 @@
-[[[{id: X,
- match: true,
- filename: Y,
- timestamp: 946728000,
- date_relative: 2000-01-01,
- tags: [inbox,signed],
- headers: {Subject: test signed message 001,
- From: Notmuch Test Suite test_su...@notmuchmail.org,
- To: test_su...@notmuchmail.org,
- Cc: ,
- Bcc: ,
- Date: 01 Jan 2000 12:00:00 -},
- body: [{id: 1,
- sigstatus: [{status: good,
- fingerprint: 5AEAB11F5E33DCE875DDB75B6D92612D94E46381,
- created: 946728000}],
- content-type: multipart/signed,
- content: [{id: 2,
- content-type: text/plain,
- content: This is a test signed message.\n},
- {id: 3,
- content-type: application/pgp-signature}]}]},
- [
+[]
FAIL signature verification with full owner trust
--- crypto.3.expected 2011-05-31 17:30:47.0 +
+++ crypto.3.output 2011-05-31 17:30:47.0 +
@@ -1,24 +1 @@
-[[[{id: X,
- match: true,
- filename: Y,
- timestamp: 946728000,
- date_relative: 2000-01-01,
- tags: [inbox,signed],
- headers: {Subject: test signed message 001,
- From: Notmuch Test Suite test_su...@notmuchmail.org,
- To: test_su...@notmuchmail.org,
- Cc: ,
- Bcc: ,
- Date: 01 Jan 2000 12:00:00 -},
- body: [{id: 1,
- sigstatus: [{status: good,
- fingerprint: 5AEAB11F5E33DCE875DDB75B6D92612D94E46381,
- created: 946728000,
- userid: Notmuch Test Suite test_su...@notmuchmail.org
(INSECURE!)}],
- content-type: multipart/signed,
- content: [{id: 2,
- content-type: text/plain,
- content: This is a test signed message.\n},
- {id: 3,
- content-type: application/pgp-signature}]}]},
- [
+[]
FAIL signature verification with signer key unavailable
--- crypto.4.expected 2011-05-31 17:30:47.0 +
+++ crypto.4.output 2011-05-31 17:30:47.0 +
@@ -1,23 +1 @@
-[[[{id: X,
- match: true,
- filename: Y,
- timestamp: 946728000,
- date_relative: 2000-01-01,
- tags: [inbox,signed],
- headers: {Subject: test signed message 001,
- From: Notmuch Test Suite test_su...@notmuchmail.org,
- To: test_su...@notmuchmail.org,
- Cc: ,
- Bcc: ,
- Date: 01 Jan 2000 12:00:00 -},
- body: [{id: 1,
- sigstatus: [{status: error,
- keyid: 6D92612D94E46381,
- errors: 2}],
- content-type: multipart/signed,
- content: [{id: 2,
- content-type: text/plain,
- content: This is a test signed message.\n},
- {id: 3,
- content-type: application/pgp-signature}]}]},
- [
+[]
PASS emacs delivery of encrypted message with attachment
FAIL decryption, --format=text
--- crypto.6.expected 2011-05-31 17:30:48.0 +
+++ crypto.6.output 2011-05-31 17:30:48.0 +
@@ -1,25 +1 @@
- message{ id:X depth:0 match:1 filename:X
- header{
-Notmuch Test Suite test_su...@notmuchmail.org (2000-01-01)
(encrypted inbox)
-Subject: test encrypted message 001
-From: Notmuch Test Suite
Re: Decryption fails
On Mon, 30 May 2011 21:30:03 +0200, Felix Geller fgel...@gmail.com wrote: starts eating all my CPU and doesn't return. Doing it on the command line using gpg directly or going through Emacs' epa works fine. Most of the test cases in crypto fail as well, but I'm not sure which ones are actually supposed to work. I can't help much with MacOS X, but all of the test cases should work with gmime 2.4.24 (at least they do for people on Debian). d ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
