From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Getting GPG working in Sup
Date: Tue, 25 Mar 2014 08:44:05 +0100 [thread overview]
Message-ID: <1395733057-sup-3470@qwerzila> (raw)
In-Reply-To: <CA+ds9g+WyYb1upUs9Kb1BFX2xXj7J3SwRddjJd9vRpGnv50fDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
Excerpts from James Pearson's message of 2014-03-25 01:41:16 +0100:
> I recently decided that I should start using GPG, primarily for signing
> messages (not encrypting them). I'm looking at
> https://github.com/sup-heliotrope/sup/wiki/gpg , and while I think I've got
> everything set correctly, test messages aren't being signed.
>
> # .sup/config.yaml
> 1 ---
> 2 :accounts:
> 3 :default:
> [...]
> 9 :gpgkey: '58DAFDEB'
I don't use quotes, but don't know if it matters.
>
> # .sup/hooks/crypto-mode.rb
> 1 crypto_selector.set_to :sign
>
> [$]> gem list | grep gpg
> gpgme (2.0.5, 2.0.2)
I'm using 2.0.5. What is the output of `rake test` in sup.git? It runs
through a few gpg-tests as well. Could you cd to sup.git/test and do:
$ ruby -I. -w test_crypto.rb -v
Do you have gpg installed? What does sup tell you about the signature of
this message (just below header)?
>
> and that should be it, right? But when I send an email to myself, I don't
> get prompted for my GPG passphrase, and I don't see an .asc on the
> receiving side.
>
> Any tips? I'm using sup 0.15.4.
Is the crypto-selector visible in edit-mode? Is 'sign' selected?
- gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-25 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 0:41 James Pearson
2014-03-25 7:44 ` Gaute Hope [this message]
2014-04-03 1:00 ` James Pearson
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=1395733057-sup-3470@qwerzila \
--to=eg@gaute.vetsj.com \
--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