Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Todd Eisenberger <sup-bugs@masanjin.net>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [issue100] GPG Signing Bug
Date: Tue, 11 May 2010 00:18:46 -0400	[thread overview]
Message-ID: <1273551419-sup-9803@zyrg.net> (raw)
In-Reply-To: <1273288706.87.0.318581427994.issue100@masanjin.net>

Excerpts from Todd Eisenberger's message of 2010-05-07 23:18:27 -0400:
> After having a few messages fail verification on the recipient end, I discovered 
> that sup is not compliant with the RFC for signing email with PGP/GPG.  RFC2015 
> section 3 indicates that signed messages must be sent in a 7-bit format such as 
> base64 or quoted-printable.  Attached is a patch to provide compliance by 
> converting to base64 when crypto is used.  Note: I am unfamiliar with the code 
> base, so it is possible this patch is not correct.

Thanks, applied to master.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


      reply	other threads:[~2010-05-11  4:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-08  3:18 Todd Eisenberger
2010-05-11  4:18 ` Rich Lane [this message]

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=1273551419-sup-9803@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=sup-bugs@masanjin.net \
    --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