From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] gpg signing issue
Date: Wed, 27 Feb 2008 09:50:37 -0800 [thread overview]
Message-ID: <1204134542-sup-7286@south> (raw)
In-Reply-To: <1204101423-sup-3529@ausone.inria.fr>
Reformatted excerpts from nicolas.pouillard's message of 2008-02-27:
> That's a ruby-mail bug with a working patch [1], however
> ruby-mail is no longer actively maintained :(
I did hear from Matt Armstrong recently that he was starting to maintain
it again. At least, he released a 1.0.0 last month that has Ruby 1.9
modifications. But nothing since.
> [1]: "[2661] set_boundary doubles quotes in params which already contained a
> quote"
> http://rubyforge.org/tracker/index.php?func=detail&aid=2661&group_id=446&atid=1756
Does the following workaround help? (Completely untested.)
diff --git a/lib/sup/crypto.rb b/lib/sup/crypto.rb
index 9e16132..ee06958 100644
--- a/lib/sup/crypto.rb
+++ b/lib/sup/crypto.rb
@@ -40,7 +40,7 @@ class CryptoManager
raise Error, (output || "gpg command failed: #{cmd}") unless $?.success?
envelope = RMail::Message.new
- envelope.header["Content-Type"] = 'multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1'
+ envelope.header["Content-Type"] = 'multipart/signed; protocol=application/pgp-signature; micalg=pgp-sha1'
envelope.add_part payload
signature = RMail::Message.make_attachment output, "application/pgp-signature", nil, "signature.asc"
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-02-27 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 3:40 Jan Spakula
2008-02-27 8:39 ` Nicolas Pouillard
2008-02-27 17:50 ` William Morgan [this message]
2008-02-27 18:56 ` Jan Spakula
2008-02-28 17:09 ` 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=1204134542-sup-7286@south \
--to=wmorgan-sup@masanjin.net \
/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