[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem

To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
From: Hamish D <dmishd@gmail.com>
Date: Sun, 30 Jan 2011 23:57:03 +0000
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
Delivered-to: eg@gaute.vetsj.com
Delivered-to: sup-devel@rubyforge.org
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=
In-reply-to: <1291023322-sup-8457@meteor.durcheinandertal.local>
List-archive: <http://rubyforge.org/pipermail/sup-devel>
List-help: <mailto:sup-devel-request@rubyforge.org?subject=help>
List-id: Sup developer discussion <sup-devel.rubyforge.org>
List-post: <mailto:sup-devel@rubyforge.org>
List-subscribe: <http://rubyforge.org/mailman/listinfo/sup-devel>, <mailto:sup-devel-request@rubyforge.org?subject=subscribe>
List-unsubscribe: <http://rubyforge.org/mailman/options/sup-devel>, <mailto:sup-devel-request@rubyforge.org?subject=unsubscribe>
References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com> <AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com> <AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com> <1289466286-sup-7540@meteor.durcheinandertal.local> <AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com> <1289907535-sup-3989@meteor.durcheinandertal.local> <AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com> <1289932061-sup-96@meteor.durcheinandertal.local> <AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com> <AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com> <1291023322-sup-8457@meteor.durcheinandertal.local>
Reply-to: Sup developer discussion <sup-devel@rubyforge.org>
Sender: 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

Follow-Ups:
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Hamish D <dmishd@gmail.com>

References:
- [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Hamish D <dmishd@gmail.com>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Hamish D <dmishd@gmail.com>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Hamish D <dmishd@gmail.com>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Gaudenz Steinlin <gaudenz@soziologie.ch>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Hamish D <dmishd@gmail.com>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Gaudenz Steinlin <gaudenz@soziologie.ch>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Hamish D <dmishd@gmail.com>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Gaudenz Steinlin <gaudenz@soziologie.ch>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Hamish D <dmishd@gmail.com>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Hamish D <dmishd@gmail.com>
- Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
  - From: Gaudenz Steinlin <gaudenz@soziologie.ch>

Prev by Date: [sup-devel] more gpgme fixes
Next by Date: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Previous by thread: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Next by thread: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Index(es):
- Date
- Thread