From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] [Heliotrope/Turnsole] GPG signature verification
Date: Thu, 01 Mar 2012 12:58:24 +0100 [thread overview]
Message-ID: <1330602132-sup-2087@stapelberg.de> (raw)
Hi,
Before I can actually switch to Heliotrope/Turnsole, I need to have GPG working
properly. I tried implementing GPG signature verification first, and got it
nearly working, but before I go down the rabbit hole too far, I decided to ask
a few questions here first:
1) In ChunkParser#chunks_for_message, the message object has multiple parts,
which in turn are just hashes. At least in my tests, the first part usually
has a "content" entry, but the second part doesn’t. Therefore, I need to
request it from heliotrope. Should I introduce a new class for that or am I
missing an existing class which I can use for that? Chunk::Attachment has
very similar functionality with its content method.
2) For verification, I need the not-decoded MIME part, but heliotrope decodes
MIME parts. Thus, I always get a bad signature. How should we fix this? Not
decode MIME in heliotrope, but in turnsole? Decode MIME in both? Make
turnsole get the raw message, too, for GPG (roundtrip alert!)?
Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2012-03-01 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 11:58 Michael Stapelberg [this message]
2012-03-05 22:45 ` William Morgan
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=1330602132-sup-2087@stapelberg.de \
--to=michael+sup@stapelberg.de \
--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