From: "Vojtěch Aschenbrenner" <vojtech@aschenbrenner.cz>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Password handling with gpg-agent
Date: Sat, 21 Aug 2010 10:20:15 +0200 [thread overview]
Message-ID: <1282378728-sup-9180@nb-asch> (raw)
In-Reply-To: <1282377608-sup-3154@nb-asch>
[-- Attachment #1.1: Type: text/plain, Size: 542 bytes --]
Excerpts from Vojtěch Aschenbrenner's message of Sat Aug 21 10:04:36 +0200 2010:
> Hey folks,
>
> I'd like to know, how to use comfortable gpg-agent with sup. I have
> gpg-agent started, use gpg-agent option in gpg.conf and pinentry program
> saved in gpg-agent.conf. But when I send signed email it everytime asks
> for password, so saving password to agent is not working!?
>
> Thank you for your help.
OK, I solved it myself :-). The problem was, that the run-mailcap wasn't
installed and some error ocurred, so password wasn't saved.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-08-21 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 8:04 Vojtěch Aschenbrenner
2010-08-21 8:20 ` Vojtěch Aschenbrenner [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=1282378728-sup-9180@nb-asch \
--to=vojtech@aschenbrenner.cz \
--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