* [sup-talk] GPG (outgoing)
@ 2010-04-11 10:30 Ian Smith
2010-04-14 13:04 ` William Morgan
2010-04-14 13:30 ` Sven Schober
0 siblings, 2 replies; 4+ messages in thread
From: Ian Smith @ 2010-04-11 10:30 UTC (permalink / raw)
To: sup-talk
[-- 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] GPG (outgoing)
2010-04-11 10:30 [sup-talk] GPG (outgoing) Ian Smith
@ 2010-04-14 13:04 ` William Morgan
2010-04-14 13:30 ` Sven Schober
1 sibling, 0 replies; 4+ messages in thread
From: William Morgan @ 2010-04-14 13:04 UTC (permalink / raw)
To: sup-talk
Reformatted excerpts from Ian Smith's message of 2010-04-11:
> 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.
I would compare the output of sup, hushmail and enigmail on a similar
message, and see if there's anything obviously different in the MIME
structure. It's possible Sup is emitting something they don't like.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] GPG (outgoing)
2010-04-11 10:30 [sup-talk] GPG (outgoing) Ian Smith
2010-04-14 13:04 ` William Morgan
@ 2010-04-14 13:30 ` Sven Schober
2010-04-15 1:00 ` Ian Smith
1 sibling, 1 reply; 4+ messages in thread
From: Sven Schober @ 2010-04-14 13:30 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 758 bytes --]
Hi!
Excerpts from Ian Smith's message of 2010-04-11 12:30:59 +0200:
> 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.
>
+1
> Thanks,
>
> Ian
>
Ciao,
Sven
--
Sven Schober, sven.schober@uni-ulm.de |UNI ULM
http://www-vs.informatik.uni-ulm.de/dept/staff/schober/ |DISTRIBUTED
Room O27-346, Phone: +49-731-5024146 |SYSTEMS LAB
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] GPG (outgoing)
2010-04-14 13:30 ` Sven Schober
@ 2010-04-15 1:00 ` Ian Smith
0 siblings, 0 replies; 4+ messages in thread
From: Ian Smith @ 2010-04-15 1:00 UTC (permalink / raw)
To: sup-talk
On further testing, removing my signatures (the bit at the bottom of emails,
not the digital type) makes Engimail happy. I'm still not sure what hushmail's
problem is, but I'm working on that, as well. So my guess is that sup doesn't
sign the signature of a message, just what it considers to be the body.
Ian
Excerpts from Sven Schober's message of Wed Apr 14 09:30:25 -0400 2010:
> Hi!
>
> Excerpts from Ian Smith's message of 2010-04-11 12:30:59 +0200:
> > 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.
> >
> +1
>
> > Thanks,
> >
> > Ian
> >
> Ciao,
> Sven
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-04-15 1:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-11 10:30 [sup-talk] GPG (outgoing) Ian Smith
2010-04-14 13:04 ` William Morgan
2010-04-14 13:30 ` Sven Schober
2010-04-15 1:00 ` Ian Smith
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox