Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Paul Grove <paul.a.grove@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel]  Sign and encrypt
Date: Mon, 16 May 2011 22:56:56 +0100	[thread overview]
Message-ID: <1305582172-sup-2519@localhost> (raw)


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

Hi I hope you guys can help me, recently I pulled the latest changes to
sup.

It took me a while - but I've noticed that I have problems when signing
and encrypting.

When I sign my emails are signed.
When I encrypt my emails are encrypted.

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.

I had a look at the code, unfortunately I'm not well versed in ruby. I
cannot see for certain if there is a problem.

I can see that when signing the code produces a signature and attaches
it to the email, but when encrypting and signing it doesn't jump through
this hoop of adding any sort of attachment and instead an extra parameter 
:sign => true is passed to pgpme when doing the encryption.

Now completely off the top of my head but wasnt it a fairly recent
change to start using pgpme? I seem to remember some discussion on
changing to it, and perhaps the version I was using is prior to this?

Thanks,

Paul Grove

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

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

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

             reply	other threads:[~2011-05-16 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 21:56 Paul Grove [this message]
2011-05-22 21:34 ` Hamish

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=1305582172-sup-2519@localhost \
    --to=paul.a.grove@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