[sup-talk] PGP INLINE

* [sup-talk] PGP INLINE - can't make it work
@ 2010-02-26 17:08 kosmici-atakuja
  2010-02-26 17:43 ` Sven Schober
  0 siblings, 1 reply; 16+ messages in thread
From: kosmici-atakuja @ 2010-02-26 17:08 UTC (permalink / raw)
  To: sup-talk

First of wall I want to say I absolutely love sup! I used all the major mail 
clients like mutt, claws, thunderbird, kmail. All mail clients just fail (mutt 
was the closest though...). Sup so far has the potential to be the best of 
them. If only I can get it to read the inline gpg that enigmail makes...

Example email looks like this in sup: 

 -----BEGIN PGP MESSAGE-----
  Charset: UTF-8
  Version: GnuPG v1.4.9 (MingW32)
  Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

  hQIOA3WKxDKSmLd7EAf/cKH72GNHWgkY46sjHuYBlV5Q9udlmjB1ucTqtVfSUysH
[cut]
 NYqMmmJ1HHG58B9bPqGFPNe/jEPeiiqj9Ez58kYzS32VeelJFwV+O8K9/TAvG4HN
  fEIgtYMGj0Uc5v0eZ7yVqFfluJrEX5V7mN2InahTCD+uFEfguvld8rZagEtlyxU5
  =nAMm
  -----END PGP MESSAGE-----

And it gets displayed like this, no error messages or anything. I have 
configured my gpg in sup as per this wiki page:
http://sup.rubyforge.org/wiki/wiki.pl?GPG
(with the numeric ID and such). 

And I enabled verbose debug logging, here's the log:
(cutting leading timestamp for better reading)

using character set encoding "UTF-8"
No 'chronic' gem detected. Install it for date/time query restrictions.
No 'ncursesw' gem detected. Install it for wide character support.
dynamically loading setlocale() from libc.so.6
setting locale...
using xapian index
locking /home/piotr/.sup/lock...
crypto: detected gpg binary in /usr/bin/gpg
starting curses
initializing log buffer
Welcome to Sup! Log level is set to debug.
initializing inbox buffer
ready for interaction!
colormap: for color twiddle_color, using id 1 -> 4, -1
colormap: for color status_color, using id 2 -> 7, 4
colormap: for color tagged_color_highlight, using id 3 -> 3, 6
colormap: for color date_color_highlight, using id 4 -> 0, 6
colormap: for color to_me_color_highlight, using id 5 -> 2, 6
colormap: for color tagged_color, using id 6 -> 3, -1
colormap: for color date_color, using id 7 -> 7, -1
colormap: for color to_me_color, using id 8 -> 2, -1
colormap: for color snippet_color, using id 9 -> 6, -1
scanning maildir /home/piotr/Mail...
done scanning maildir
crypto: running: /usr/bin/gpg --quiet --batch --no-verbose --logger-fd 1 --
use-agent --output /tmp/32042-0-redwood.outp
scanning maildir /home/piotr/Mail...
done scanning maildir
crypto: running: /usr/bin/gpg --quiet --batch --no-verbose --logger-fd 1 --
use-agent --output /tmp/32042-0-redwood.outp
crypto: running: /usr/bin/gpg --quiet --batch --no-verbose --logger-fd 1 --
use-agent --output /tmp/32042-2-redwood.outp
crypto: running: /usr/bin/gpg --quiet --batch --no-verbose --logger-fd 1 --
use-agent --output /tmp/32042-0-redwood.outp
colormap: for color alternate_patina_color, using id 10 -> 0, 4
colormap: for color message_patina_color, using id 11 -> 0, 2
colormap: for color system_buf_color_highlight, using id 12 -> 7, 6

(no errors there as far as I can see... And looks like it's running the gpg 
binary succesfully... I just changed the maildir path for privacy in this log)

GPG is configured to use gpg-agent, the gpg-agent is running, pinentry program 
shows up when running sup and I enter the correct password. I checked the 
password many times already. Also, the environment variable $GPG_AGENT_INFO is 
present and visible in sup environment (it's global and visible anywhere). 
I already tried it without "use gpg-agent" and the effect was the same. 

In mutt this worked, I mean the inline gpg messages were decrypted using this 
same setup of gpg-agent and gpg. It also works in kmail (although not 
perfectly, but decodes the messages).

Now, this may be a clue: when normal gpg message is used (mime) it sometimes 
geta decrypted and sometimes doesn't. If it doesn't, sup only says this in the 
message: 
    x This message has been decrypted for display
    x Attachment: sup-attachment-1267203299-4513. (multipart/mixed; 71b)

When I'm trying to display this attachment it says: 
For some bizarre reason, RubyMail was unable to parse this attachment.
and in the status line:
Couldn't execute view command, viewing as text.

(this may be because I have no run-mailcap file, but the message was in plain 
text, no html, so it shouldn't be needed now should it? I'm planning on 
getting some run-mailcap script from some debian system when I have some time, 
but for now this inline GPG is my main priority)

I'm still not sure why they sometimes decrypt correctly and sometimes not, but 
I can work with this, at least it works sometimes. But even when mime gpg 
works, the inline stuff doesn't. 

Verisions:
I'm using sup version 0.10.2 from Archlinux AUR. 
ruby version is 1.9.1
xapian-core is 1.0.18

Is there anything I can do to get this working? This is a crucial feature for 
me as almost all my work colleagues use thunderbird and enigmail to send their 
email and that uses inline pgp crap as default (which I know is not conforming 
to any standards etc.). And even if I can convince verybody to switch to mime, 
I still have a couple hundred megs of archives in this damn format. 

Moreover, I searched the list archives and it looks like some people have got 
it working as there have been patches to make it work a couple of months ago. 
And my version is recent (January) so those patches should be in it. It just 
doesn't for me for some reason :(

I know I should read crypto.rb and figure it out from there. I tried, I just 
can't understand it, as I'm not experienced in ruby, or email clients code for 
that matter. 

Please help!
Thank you
Piotr
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

^ permalink raw reply	[flat|nested] 16+ messages in thread