From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.240.136 with SMTP id la8cs110946icb; Sun, 30 Jan 2011 16:34:26 -0800 (PST) Received: by 10.229.88.200 with SMTP id b8mr1522837qcm.246.1296434065422; Sun, 30 Jan 2011 16:34:25 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id w17si24509891vcf.101.2011.01.30.16.34.25; Sun, 30 Jan 2011 16:34:25 -0800 (PST) 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 DCBFF1779949; Sun, 30 Jan 2011 19:34:24 -0500 (EST) Received: from mail-qw0-f50.google.com (mail-qw0-f50.google.com [209.85.216.50]) by rubyforge.org (Postfix) with ESMTP id 82232185834E for ; Sun, 30 Jan 2011 18:57:04 -0500 (EST) Received: by qwd6 with SMTP id 6so4986915qwd.23 for ; Sun, 30 Jan 2011 15:57:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=88vDv+m51MfdG2pHc20Gg4tjE0gHDxJTVPFp/17tVRw=; b=Unu/jn+By6R1JK4ceoutA0sX4ylW2JNLexg85KEwEAkA8XQUJ3K2ayD4kEAjCqBMW7 PTbEIhjHp7Kb/WJe8ws4zRtwg0FOC+csTtwYV0NjikzBI04Vd6L76iXNAIPYVeu6YXzO ccaAvwsbLiFlJE2JDvYO5CgedeWBRDTLjD/6g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Ka1j30k/W4kf9s7H2I/i8+buS4A0+8vgbcJpP548xQXi5waax8uMPb3eL4PUpEGdpv 23ul2RAR+iB4NhTwyGAF/GIQ+FhJDMZTZR6mBYv+9t2/bp2yu7CbXYWetXfALw3BMTNv +QuFTGUgLZZVam/kRqBqjJt0dWGj/T/eKB9j0= MIME-Version: 1.0 Received: by 10.229.96.70 with SMTP id g6mr3491683qcn.254.1296431823711; Sun, 30 Jan 2011 15:57:03 -0800 (PST) Received: by 10.229.218.79 with HTTP; Sun, 30 Jan 2011 15:57:03 -0800 (PST) In-Reply-To: <1291023322-sup-8457@meteor.durcheinandertal.local> References: <1289466286-sup-7540@meteor.durcheinandertal.local> <1289907535-sup-3989@meteor.durcheinandertal.local> <1289932061-sup-96@meteor.durcheinandertal.local> <1291023322-sup-8457@meteor.durcheinandertal.local> Date: Sun, 30 Jan 2011 23:57:03 +0000 Message-ID: From: Hamish D To: Sup developer discussion Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org > I just discovered another problem: If the secret key is not available > (because it's on a removable media and the media is not mounted), the > mail is sent anyway. While this is just a bit annoying for signed mail > it definitely should not happen for encrypted mails. Current sup > corectly fails in this case. Finally got around to fixing this issue. I think it may be a bug in the gpgme gem which I'll investigate further at some point. In the meantime, I've worked out how to get sup to stop this being a problem. The fix has been applied to next, and will hopefully move to master before too long. http://www.mail-archive.com/sup-devel@rubyforge.org/msg00899.html Hamish _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel