From: Gaudenz Steinlin <gaudenz@soziologie.ch>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Date: Mon, 29 Nov 2010 10:41:35 +0100 [thread overview]
Message-ID: <1291023322-sup-8457@meteor.durcheinandertal.local> (raw)
In-Reply-To: <AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1537 bytes --]
Hi Hamish
Excerpts from Hamish D's message of Son Nov 28 23:51:43 +0100 2010:
> OK, here is a set of 4 patches that implement the change over to the
> gpgme library. There's quite a bit of work in there so I thought I'd
> leave it as a few patches, but I have done some tidying.
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.
It would also be nice to have different colors for different trust
levels. So you don't have to expand the extra information to see if a
valid signature is trusted or not. Is this already possible with the
current hook?
>
> I have some more ideas for improvements, but I'm happy that this
> reproduces the behaviour of using the gpg binary, and I find sup usage
> much smoother with this change.
>
> I'll leave it for others to decide whether to stick this in sup 0.12 -
> I guess it could be risky to stick it in without it being tested, but
> maybe it could be applied to the next tree, and then moved to main
> after 0.12 has been released.
As far as I understood the branch layout the flow of changes is master
-> next -> release. So applying to next would mean it ends up in the
next release (0.12).
Gaudenz
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-11-29 10:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 20:08 Hamish D
2010-11-08 11:21 ` Hamish D
2010-11-08 22:32 ` Hamish D
2010-11-11 9:09 ` Gaudenz Steinlin
2010-11-11 17:25 ` Hamish D
2010-11-16 11:42 ` Gaudenz Steinlin
2010-11-16 14:20 ` Hamish D
2010-11-16 18:36 ` Gaudenz Steinlin
2010-11-16 23:05 ` Hamish D
2010-11-28 22:51 ` Hamish D
2010-11-29 9:41 ` Gaudenz Steinlin [this message]
2010-11-30 6:22 ` Tero Tilus
2010-12-01 8:37 ` Gaudenz Steinlin
2010-12-06 23:31 ` Hamish D
2010-12-23 18:43 ` Rich Lane
2011-01-19 3:11 ` Rich Lane
2011-01-30 23:57 ` Hamish D
2011-01-30 23:59 ` Hamish D
2011-01-19 16:12 ` Alvaro Herrera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1291023322-sup-8457@meteor.durcheinandertal.local \
--to=gaudenz@soziologie.ch \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox