On 09/23/2013 07:23 PM, Simon Hirscher wrote:
> Now, in order for you to test that behavior I'm going to send you a
> signed and encrypted message because that should exactly reproduce the
> bug, as long as you don't import my key (id EBACABE5 /
> http://simonhirscher.de/public_key.asc) for
Hi Daniel,
First of all, sorry for the delay ? I had locked myself out from
everything digital to study for my exams.
On Thu, Sep 5, 2013 at 5:03 PM, Daniel Kahn Gillmor
wrote:
> I just tried to replicate this, and i do not see this misbehavior. I'm
> using notmuch 0.16-1 on a debian
Hi Daniel,
First of all, sorry for the delay – I had locked myself out from
everything digital to study for my exams.
On Thu, Sep 5, 2013 at 5:03 PM, Daniel Kahn Gillmor
d...@fifthhorseman.net wrote:
I just tried to replicate this, and i do not see this misbehavior. I'm
using notmuch 0.16-1
On 09/23/2013 07:23 PM, Simon Hirscher wrote:
Now, in order for you to test that behavior I'm going to send you a
signed and encrypted message because that should exactly reproduce the
bug, as long as you don't import my key (id EBACABE5 /
http://simonhirscher.de/public_key.asc) for signature
Simon Hirscher writes:
>
> $ gpg --recv-keys
>
> $ notmuch show --decrypt id:xyz at example.com
>
> [?]
> Hey there,
> Now the decryption worked!
> [?]
>
Is this related to Jamie's report?
id:87obwrix8s.fsf at servo.finestructure.net
Jamie, did you ever narrow down the gmime
Simon Hirscher pub...@simonhirscher.de writes:
$ gpg --recv-keys sender's key
$ notmuch show --decrypt id:x...@example.com
[…]
Hey there,
Now the decryption worked!
[…]
Is this related to Jamie's report?
id:87obwrix8s@servo.finestructure.net
Jamie, did you ever narrow down the
Hi Simon--
On 09/04/2013 06:01 PM, Simon Hirscher wrote:
> This is now the second time the following has happened to me:
[ decryption failure until adding sender's key]
> Also, I should add that manually decrypting the message with gpg (i.e.
> without using notmuch) already worked *before* I
Dear notmuch developers,
This is now the second time the following has happened to me:
#
$ notmuch show --decrypt id:xyz at example.com
message{ id:xyz at example.com depth:0 match:1 excluded:0
filename:/home/simon/***
header{
John Doe (Today 21:52) (encrypted inbox new)
Subject:
Hi Simon--
On 09/04/2013 06:01 PM, Simon Hirscher wrote:
This is now the second time the following has happened to me:
[ decryption failure until adding sender's key]
Also, I should add that manually decrypting the message with gpg (i.e.
without using notmuch) already worked *before* I
Dear notmuch developers,
This is now the second time the following has happened to me:
#
$ notmuch show --decrypt id:x...@example.com
message{ id:x...@example.com depth:0 match:1 excluded:0 filename:/home/simon/***
header{
John Doe sen...@example.com (Today 21:52) (encrypted inbox new)
On Thu, 02 Jun 2011 08:35:49 -0700, Jameson Graef Rollins 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
On Thu, 02 Jun 2011 18:49:22 +0200, Felix Geller 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
On Tue, 31 May 2011 19:33:29 +0200, Felix Geller 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
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
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
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
On Tue, 31 May 2011 00:18:26 -0700, Jameson Graef Rollins 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
On Mon, 30 May 2011 21:30:03 +0200, Felix Geller wrote:
> Most of the test cases in crypto fail as well, but I'm not sure which
> ones are actually supposed to work.
Hey, Felix. As David said, all crypto tests should be passing with
libgmime 2.4.24. It would probably be instructive to know
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
Hi all,
I'm using a version of notmuch based on cb84187 from the master branch
on notmuchmail.org/git/notmuch and am accessing it mostly through the
Emacs UI. Signature verification seems to work nicely, only decryption
fails for any message/thread that I've tried it on. The respective
notmuch
On Mon, 30 May 2011 21:30:03 +0200, Felix Geller 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
Hi all,
I'm using a version of notmuch based on cb84187 from the master branch
on notmuchmail.org/git/notmuch and am accessing it mostly through the
Emacs UI. Signature verification seems to work nicely, only decryption
fails for any message/thread that I've tried it on. The respective
notmuch
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
23 matches
Mail list logo