A snippet from 90gpg-agent reads like this.
# Invoking gpg-agent with no arguments exits successfully if the agent
# is already running as pointed by $GPG_AGENT_INFO
if ! $GPGAGENT 2>/dev/null; then
STARTUP="$GPGAGENT --daemon --sh --write-env-file=$PID_FILE $STARTUP"
fi
That's
this is only a problem if the setting of $GPG_AGENT_INFO differ between
$PID_FILE and what's already in the environment variable prior to
sourcing $PID_FILE or am I overlooking something? does this ever
happen?
** Changed in: gnupg2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnup
I just posted an explanation on the thread of the related bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/804641
Title:
gpg-agent incorrectly detects currently running daemons
To manage n
Since gpg-agent is being run through the $STARTUP chain, sourcing that
$PID_FILE seems unnecessary if gpg-agent gets actually invoked by this
script. If I get things correctly, this sourcing part of the script is
only intended to recover access to a (leftover?) gpg-agent that is
already running whe
