[
https://issues.apache.org/jira/browse/ACCUMULO-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418222#comment-15418222
]
Christopher Tubbs commented on ACCUMULO-4400:
---------------------------------------------
Limitations:
# This will force the password to be input at the beginning of the build.sh
script, unless the user is using some persistent cache like
gnome-keyring-daemon to manage one's key.
# If the user pauses at the prompts later in the script, for a long period of
time, the cache could still expire during execution, even if the cache is reset
at the start of the script.
# The build.sh script still presumes that gpg-agent is configured with a
sufficiently large enough {{default-cache-ttl}} and {{max-cache-ttl}} values,
so that the cache won't expire during the creation of the release candidate.
> Attempt to clear gpg cache to reset timeouts in gpg-agent before build in
> build.sh
> ----------------------------------------------------------------------------------
>
> Key: ACCUMULO-4400
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4400
> Project: Accumulo
> Issue Type: Task
> Components: build
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Fix For: 1.6.6, 1.7.3, 1.8.1, 1.9.0
>
>
> If gpg-agent has already cached one's gpg key, the max timeout may be reached
> prior to completion of a release candidate build.
> build.sh should attempt to clear the gpg-agent cache so the gpg passphrase
> will still be sufficiently "fresh" in the agent for the full duration of the
> build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
