From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Sascha Silbe <sascha-ml-reply-to-2011-1@silbe.org>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] use gpg2 (GnuPG 2.x) instead of gpg (GnuPG 1.x)
Date: Tue, 11 Jan 2011 12:45:09 -0300 [thread overview]
Message-ID: <1294760149-sup-8106@alvh.no-ip.org> (raw)
In-Reply-To: <1294759313-653-1-git-send-email-sascha-pgp@silbe.org>
Excerpts from Sascha Silbe's message of mar ene 11 12:21:53 -0300 2011:
> Since 1.9.14 GnuPG can automatically start gpg-agent if it's not already
> running (using a well-known socket location). When using GnuPG 1.x gpg-agent
> needs to already be running at the time sup is started because the socket
> location is random and passed via environment variables.
>
> Autostarting gpg-agent is particularly convenient when using sup via ssh
> as gpg-agent would need to be started manually otherwise (for local X
> sessions OTOH it's often started automatically by distro scripts).
I think it should fall back to using `which gpg` in case gpg2 is not
available.
--
Álvaro Herrera <alvherre@alvh.no-ip.org>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-01-11 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 15:21 Sascha Silbe
2011-01-11 15:34 ` Ben Walton
2011-01-11 15:45 ` Alvaro Herrera [this message]
2011-01-11 18:30 ` Sascha Silbe
2011-01-11 18:59 ` [sup-devel] [PATCH v2] prefer gpg2 (GnuPG 2.x) over " Sascha Silbe
2011-01-11 20:20 ` Gaudenz Steinlin
2011-01-18 18:20 ` Sascha Silbe
2011-01-19 3:37 ` Rich Lane
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=1294760149-sup-8106@alvh.no-ip.org \
--to=alvherre@alvh.no-ip.org \
--cc=sascha-ml-reply-to-2011-1@silbe.org \
--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