From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs26698fgb; Mon, 8 Mar 2010 02:30:26 -0800 (PST) Received: by 10.224.58.98 with SMTP id f34mr2247543qah.351.1268044225697; Mon, 08 Mar 2010 02:30:25 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 4si11791307qwe.6.2010.03.08.02.30.25; Mon, 08 Mar 2010 02:30:25 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id B287D1588081; Mon, 8 Mar 2010 05:30:11 -0500 (EST) Received: from m157.home.net.pl (m157.home.net.pl [62.129.253.157]) by rubyforge.org (Postfix) with SMTP id 8B673185826F for ; Mon, 8 Mar 2010 05:29:50 -0500 (EST) Received: from 217.98.91.13 (217.98.91.13) (HELO pk-laptop.localnet) by sigarden.home.pl (79.96.31.244) with SMTP (IdeaSmtpServer v0.70) id d854c5484924dd79; Mon, 8 Mar 2010 11:29:49 +0100 From: piotr.kempa@wp.eu To: sup-talk@rubyforge.org Date: Mon, 8 Mar 2010 11:29:47 +0100 User-Agent: KMail/1.13.1 (Linux/2.6.32-ck; KDE/4.4.1; x86_64; ; ) References: <201002261808.36354.kosmici-atakuja@wp.pl> <201003021519.23488.piotr.kempa@wp.eu> <201003081118.55543.piotr.kempa@wp.eu> In-Reply-To: <201003081118.55543.piotr.kempa@wp.eu> MIME-Version: 1.0 Message-Id: <201003081129.47648.piotr.kempa@wp.eu> Subject: Re: [sup-talk] PGP INLINE - can't make it work X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On Monday 08 March 2010 11:18:55 piotr.kempa@wp.eu wrote: > On Tuesday 02 March 2010 15:19:23 piotr.kempa@wp.eu wrote: > > Sounds cool, I can't wait then. Let's hope the patch is included in 0.1= 1. = > > Thanks Michael! > > Piotr > > = > > On Tuesday 02 March 2010 14:59:19 Michael Stapelberg wrote: > > > Hi Piotr, > > > = > > > Excerpts from piotr.kempa's message of Di M=E4r 02 11:49:59 +0100 201= 0: > > > > So, I guess if this functionality is to be included in sup (and I = think = > it = > > > > doesn't have to be since enigmail just makes broken messages and = there's = > > no = > > > > reason why anybody should put up with that:) it should not be in = > crypto.rb = > > but = > > > > somewhere else, where the decision is made to even use functions fr= om = > > > > crypto.rb (like decrypt) on a message. I'm no programmer but I gues= s = it = > > should = > > > As mentioned, I wrote a patch to do this. It is currently in review a= nd = > will > > > hopefully be included soon. > > > = > = > Can anyone confirm if this patch made it to 0.11? I just installed the ne= w = > version and it still doesn't work but if it's there then maybe I'm doing = > something wrong. If it didn't, is it posted anywhere? I'll be happy to pa= tch = > 0.11 myself instead of waiting for the next version. I really, really wan= t = to = > start using sup :) > = > Thank you, = > Piotr > = Okay, I found the patch here: http://www.mail-archive.com/sup- talk@rubyforge.org/msg02770.html And it is included in 0.11, I just checked in the code. = However, this still doesn't work because the header doesn't contain Content = Type =3D application/pgp, it is text/plain, which is absolutely crazy and I= have = no idea what the enigmail developers are thinking... Anyway, here's how it = looks like (only the important part): X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=3DUTF-8 Content-Transfer-Encoding: quoted-printable -----BEGIN PGP MESSAGE----- Charset: UTF-8 Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org =3D20 hQIOA3WKxDKSmLd7EAf9GP5JLA77IcGOAUrOZ8fGCEtK8Pm838Me+pMD94ulHlDS LcidQKPSVGXaj4lLU8RqxoMKTpxuaZAm1u286C+SL9eQc51N3gH/X57loKhjCRb+ [...] So in order to decide about encrypted content you actually have to look ins= ide = the body of the message, not just at the header. At least I couldn't find a= ny = indication in the headers :( All in all, I wouldn't be surprised if you decided not to support such brok= en = emails so I'll just go about learning enough ruby to patch it myself :) Piotr _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk