Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ian Smith <ismith@MIT.EDU>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] GPG (outgoing)
Date: Sun, 11 Apr 2010 06:30:59 -0400	[thread overview]
Message-ID: <1270981813-sup-1681@baad> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1171 bytes --]

Hi all,

I'm having some trouble getting outgoing signed and/or encrypted messages to be
accepted, and I'm hoping someone here has a suggestion.

In particular, I can sign (I've been testing mostly with signatures, not
encryption) using GPG, and send a message successfully; however, while sup
verifies that it thinks the signature is good, hushmail doesn't recognize the
message as having a signature (it sees signature.asc as an attachment, but
doesn't read the message as being signed), and correspondents tell me that
Enigmail flags my message as having a bad signature.

Previous traffic on sup-talk suggests a number of people are successfully using
gpg, so I'm a bit confused - a friend suggested that this might be because
implementation of the PGP/MIME standard varies widely between clients, so the
problem might be with hushmail and Enigmail rather than with sup or my
configuration thereof.  Can someone confirm this?  Would it help to do inline
signing and encryption rather than PGP/MIME, and if so, is there a patch in
progress to do that, or should I start diving through crypto.rb?

Thanks,

Ian

-- 
Ian Smith
ismith@mit.edu
http://www.bostonaccess.org

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

             reply	other threads:[~2010-04-11 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 10:30 Ian Smith [this message]
2010-04-14 13:04 ` William Morgan
2010-04-14 13:30 ` Sven Schober
2010-04-15  1:00   ` Ian Smith

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=1270981813-sup-1681@baad \
    --to=ismith@mit.edu \
    --cc=sup-talk@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