From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.178.13 with SMTP id a13cs37816wff; Sun, 22 May 2011 14:51:54 -0700 (PDT) Received: by 10.52.70.82 with SMTP id k18mr2534353vdu.286.1306101114095; Sun, 22 May 2011 14:51:54 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id l21si4011579vby.13.2011.05.22.14.51.53; Sun, 22 May 2011 14:51:54 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 9FFE519783BC for ; Sun, 22 May 2011 17:51:53 -0400 (EDT) Received: from mail-wy0-f178.google.com (mail-wy0-f178.google.com [74.125.82.178]) by rubyforge.org (Postfix) with ESMTP id 43DB41858346 for ; Sun, 22 May 2011 17:34:37 -0400 (EDT) Received: by wyb33 with SMTP id 33so4726601wyb.23 for ; Sun, 22 May 2011 14:34:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:subject:from:to:in-reply-to :references:date:message-id:user-agent:content-transfer-encoding; bh=IOjZaX691zo+tDuBdFCOCgylMEVUICAN3/wwwHDqihg=; b=RmWdYCfp69gGX0xn0Rlyu+ZZed4wihw71gY5fkGLq9hKg8oWgwSCOGk5Lfn5k0A5Bd +ah6AouXgGAeB4wLOoOcqGZvBgL9xoccLjYVbUWXvJ5olRzwIhSxHY8syRJ0o6S+rFZl 1LzLLe7NI0dj/Za+B5sIy40yky4vmoqc1UeAY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding; b=Jk6jgNDnKCzcZkKTh4Y5Rlr/xtIF7vtyNTrqbyyJ3XpHZDnPzUdFj8K/gj1s0X27s3 EogRHprzE/V/SngyE21MYZt28KuPKLqS1Aw+NGcSRXFldrQmBzHGIe9I7crlrnfXG3hS xbfCEYeRO+MXLHbuR+tsn6slKiKQlCgNbeJSI= Received: by 10.216.67.72 with SMTP id i50mr1574410wed.29.1306100075253; Sun, 22 May 2011 14:34:35 -0700 (PDT) Received: from localhost (cpc12-cmbg15-2-0-cust81.5-4.cable.virginmedia.com [86.30.247.82]) by mx.google.com with ESMTPS id c43sm2950672weo.42.2011.05.22.14.34.33 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 22 May 2011 14:34:34 -0700 (PDT) From: Hamish To: sup-devel In-reply-to: <1305582172-sup-2519@localhost> References: <1305582172-sup-2519@localhost> Date: Sun, 22 May 2011 22:34:31 +0100 Message-Id: <1306099840-sup-7534@whisper> User-Agent: Sup/git Subject: Re: [sup-devel] Sign and encrypt X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Excerpts from Paul Grove's message of Mon May 16 22:56:56 +0100 2011: > But when I sign _and_ encrypt my emails come out only encrypted! > > I only noticed because I post to a mailing list that requires sign and > encrypt in order to post. > > I know this problem never used to exist as I've posted on the list > before without issue. I've taken the emails produced by sup and run > them through gpg and that shows as not signed also. Interesting. I wrote the code to start using gpgme, and it's been working fine for me. I also am on an email list that requires emails to be signed and encrypted (using scheuder[0]) and my emails are accepted there. With the way I've been using gpgme the signature is embedded within the signed text, so looking at the encrypted email you just see a single block. However saving the email and running gpg against it reports that the email is both encrypted and signed for me. As to which version you are using, if you were on the master branch then you shouldn't have any of the gpgme stuff, and if you have the latest from the "next" branch then you should have the same as me. If you check you have the latest from the "next" branch and still can't generate a signed and encrypted email, then feel free to send me a signed and encrypted email using sup, and I'll pull it apart at my end. Hamish Downer [0] http://schleuder2.nadir.org/ _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel