From: Hamish D <dmishd@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Date: Tue, 16 Nov 2010 23:05:50 +0000 [thread overview]
Message-ID: <AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com> (raw)
In-Reply-To: <1289932061-sup-96@meteor.durcheinandertal.local>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
> This does not work for me when running the foobacca/gpgme tree (commit
> 7b9a1eeeaaa25931963e2de49410d7cb0c7e6772). The CryptoNotice is empty.
Oops. I had one too many flatten! calls and was using the
output_lines.flatten! as a return value. However flatten! returns nil
if there is no flattening to be done. I've now fixed this in the
github tree. Please try it out and let me know how it works for you.
>> I am also working on having extra information generated when the key
>> is not trusted, but this is not done yet. And I am also working on a
>> hook where you can generate as much information as you want from the
>> signature for the CryptoNotice. Hopefully be ready to submit before
>> the weekend.
>
> This sounds nice. Thanks for your work!
And thank you for your testing and patience :)
The github version also has the sig-output hook set up. From the hook text:
START
Runs when the signature output is being generated, allowing you to
add extra information to your signatures if you want.
Variables:
signature: the signature object (class is GPGME::Signature)
from_key: the key that generated the signature (class is GPGME::Key)
Return value: an array of lines of output
END
I've attached a sample hook file if you want to have a play with it.
I'll document this all on the wiki if it gets accepted.
I'll give you a few days to find some more problems, but if you fail
to find any then I'll package this up as a single patch and resubmit
it all.
Hamish
[-- Attachment #2: sig-output.rb --]
[-- Type: application/x-ruby, Size: 1222 bytes --]
[-- Attachment #3: 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-16 23:23 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 [this message]
2010-11-28 22:51 ` Hamish D
2010-11-29 9:41 ` Gaudenz Steinlin
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='AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com' \
--to=dmishd@gmail.com \
--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