From: Hamish <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Sign and encrypt
Date: Sun, 22 May 2011 22:34:31 +0100 [thread overview]
Message-ID: <1306099840-sup-7534@whisper> (raw)
In-Reply-To: <1305582172-sup-2519@localhost>
Excerpts from Paul Grove's message of Mon May 16 22:56:56 +0100 2011:
> But when I sign _and_ encrypt my emails come out only encrypted!
>
> I only noticed because I post to a mailing list that requires sign and
> encrypt in order to post.
>
> I know this problem never used to exist as I've posted on the list
> before without issue. I've taken the emails produced by sup and run
> them through gpg and that shows as not signed also.
Interesting. I wrote the code to start using gpgme, and it's been
working fine for me. I also am on an email list that requires emails to
be signed and encrypted (using scheuder[0]) and my emails are accepted
there.
With the way I've been using gpgme the signature is embedded within the
signed text, so looking at the encrypted email you just see a single
block. However saving the email and running gpg against it reports that
the email is both encrypted and signed for me.
As to which version you are using, if you were on the master branch then
you shouldn't have any of the gpgme stuff, and if you have the latest
from the "next" branch then you should have the same as me.
If you check you have the latest from the "next" branch and still can't
generate a signed and encrypted email, then feel free to send me a
signed and encrypted email using sup, and I'll pull it apart at my end.
Hamish Downer
[0] http://schleuder2.nadir.org/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-05-22 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 21:56 Paul Grove
2011-05-22 21:34 ` Hamish [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=1306099840-sup-7534@whisper \
--to=dmishd@gmail.com \
--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