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).
Signed-off-by: Sascha Silbe <sascha-...@silbe.org>
---
lib/sup/crypto.rb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
If there's anyone who would like to stick to GnuPG 1.x (the only advantage
is the smaller size of the binary), we might need to make this configurable
(or overridable via the gpg-args hook).
diff --git a/lib/sup/crypto.rb b/lib/sup/crypto.rb
index 537745d..916f04c 100644
--- a/lib/sup/crypto.rb
+++ b/lib/sup/crypto.rb
@@ -25,7 +25,7 @@ EOS
def initialize
@mutex = Mutex.new
- bin = `which gpg`.chomp
+ bin = `which gpg2`.chomp
@cmd = case bin
when /\S/
debug "crypto: detected gpg binary in #{bin}"
--
1.7.2.3
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
