From: Micah Anderson <micah@riseup.net>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Getting gpg to work
Date: Tue, 10 Nov 2009 18:47:18 -0500 [thread overview]
Message-ID: <87fx8mkkmx.fsf@pond.riseup.net> (raw)
In-Reply-To: <1243730754-sup-8672@entry>
William Morgan <wmorgan-sup@masanjin.net> writes:
> Reformatted excerpts from Micah Anderson's message of 2009-05-28:
>> [Fri May 29 00:17:42 -0400 2009] crypto: detected gpg binary in /usr/bin/gpg
>
> Any other obvious messages in the log about multipart/encrypted?
I failed to respond to this message, partly because I think I decided to
give up on sup at the time. But I am back now, because sup is so
alluring, and I'm trying harder to switch this time :)
This time, gpg works fine... although it is using the wrong gpg keyid
when I try to send. I did manage to find and set the gpgkey configurable
in the .sup/config.yaml:
:accounts:
:default:
:signature: /home/micah/.signature
:email: micah@riseup.net
:sendmail: /usr/sbin/sendmail -oem -ti
:name: micah anderson
:gpgkey: 0xDEADBEEF
but still, that key does not get used, and instead the first key in my
keyring for my email@address gets used instead. I do not want that,
because that key is set to expire in about a week.
micah
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-11-10 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 19:52 Micah Anderson
2009-05-27 16:25 ` William Morgan
2009-05-29 4:19 ` Micah Anderson
2009-05-31 0:48 ` William Morgan
2009-11-10 23:47 ` Micah Anderson [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=87fx8mkkmx.fsf@pond.riseup.net \
--to=micah@riseup.net \
--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