From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.241.17 with SMTP id o17cs129862wfh; Mon, 16 May 2011 14:58:29 -0700 (PDT) Received: by 10.224.27.129 with SMTP id i1mr3463773qac.312.1305583108207; Mon, 16 May 2011 14:58:28 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id mz7si10538906qcb.69.2011.05.16.14.58.27; Mon, 16 May 2011 14:58:28 -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 B76E3167832A for ; Mon, 16 May 2011 17:58:27 -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 A794D1858300 for ; Mon, 16 May 2011 17:57:06 -0400 (EDT) Received: by wyb33 with SMTP id 33so4702698wyb.23 for ; Mon, 16 May 2011 14:57:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:date:message-id:user-agent :content-transfer-encoding:mime-version:content-type; bh=jsOxxEqgzot4rEYFRcul9AJj+KKYK6v/ztKJbXKVyyI=; b=EX5y7YqESukbyzUSL9H6ylPDwPfiM7UKDPaavksnrGVOgXbTmjWj6ncjzwaaOBsUP4 UP3O2APaVPuU7y1m8f/yveizJFh2y8bsjs0PepFNAAqpz+BTUajQp74FnslcZdjcjneO pZuIWIV75aiarL0ANndOgKB8AgifrcoJI5Tbo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:date:message-id:user-agent :content-transfer-encoding:mime-version:content-type; b=c9c/nJAezK9tjUa66tDTTWIWqwNw+vb7+0E7ZyMDBXCuq/BjswhWX2b/XQnf5iECBA pTxRzoHf/a7ia1goIHRJLHHtYGBoRSQNeW1UB0eeuzlvAU5SWz/6PBuvK1D8O8DioX7U lU16J/alwsKFjJDEqteqNPLoqXarMAzZIcIbY= Received: by 10.216.67.17 with SMTP id i17mr4459486wed.101.1305583026015; Mon, 16 May 2011 14:57:06 -0700 (PDT) Received: from localhost (78-86-196-163.zone2.bethere.co.uk [78.86.196.163]) by mx.google.com with ESMTPS id f52sm2793409wes.11.2011.05.16.14.57.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2011 14:57:04 -0700 (PDT) From: Paul Grove To: sup-devel Date: Mon, 16 May 2011 22:56:56 +0100 Message-Id: <1305582172-sup-2519@localhost> User-Agent: Sup/git MIME-Version: 1.0 Subject: [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: , Content-Type: multipart/mixed; boundary="===============0362829889==" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org --===============0362829889== Content-Transfer-Encoding: 8bit Content-Type: multipart/signed; boundary="=-1305583020-889106-8400-8335-1-="; protocol="application/pgp-signature" --=-1305583020-889106-8400-8335-1-= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi I hope you guys can help me, recently I pulled the latest changes to sup. It took me a while - but I've noticed that I have problems when signing and encrypting. When I sign my emails are signed. When I encrypt my emails are encrypted. 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. I had a look at the code, unfortunately I'm not well versed in ruby. I cannot see for certain if there is a problem. I can see that when signing the code produces a signature and attaches it to the email, but when encrypting and signing it doesn't jump through this hoop of adding any sort of attachment and instead an extra parameter= = :sign =3D> true is passed to pgpme when doing the encryption. Now completely off the top of my head but wasnt it a fairly recent change to start using pgpme? I seem to remember some discussion on changing to it, and perhaps the version I was using is prior to this? Thanks, Paul Grove --=-1305583020-889106-8400-8335-1-= Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJN0Z2pAAoJEI9NtEUYlrmaY0wH/AgthFzsF8YB/Y0D5ovmf9/+ 2lfoQkypejusbZOgBRDMXNWXZEUF1NPSTfh1UZ/M2FOKTZEPXeHHQBC5UpabbOTv ckY49I3axACzMRJznhmsARdfwpix5baCH6gOrbuM4QsSx5TIhMclbIbJtARch+NG fZKQDS7UpnFj4Ir6Tw4Qt+TRQHZbKxftpIQoEw8+z4o2FtBFVufMhmT22C8nEtc1 5kBeIkM1rXweOsTbYky0LYl1WzKJcZqc4K2iMc8iYe1E8R15E6iD+pZekUp2JnFb /seEEdyFiHYCfJPvylpf15Qew7SQlraoFK2OGI5o2CWReuifQUvXrTPywpXM8QY= =l+Zr -----END PGP SIGNATURE----- --=-1305583020-889106-8400-8335-1-=-- --===============0362829889== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel --===============0362829889==--