how to disable pinentry
Cathy.Smith at pnnl.gov
Wed Feb 25 17:51:23 CET 2015
Adding this line didn't work:
The message was invalid option
gpg: /home/foo/.gunpg/gpg.conf:242: invalid option
The CentOS6 and RHEL6 distributions don't provide a /usr/bin/pinentry-tty.
One of my goals of this is to be able to set a passphrase on a key in batch processing. Perhaps, there is another way to accomplish that?
Cathy L. Smith
Pacific Northwest National Laboratory
Operated by Battelle for the
U.S. Department of Energy
Email: cathy.smith at pnnl.gov
From: Gnupg-users [mailto:gnupg-users-bounces at gnupg.org] On Behalf Of Damien Goutte-Gattat
Sent: Wednesday, February 25, 2015 1:06 AM
To: gnupg-users at gnupg.org
Subject: Re: how to disable pinentry
On 02/25/2015 02:01 AM, Smith, Cathy wrote:
> Can someone tell the how to disable pinentry? I'd like to be able to run gpg --edit-key, or to open a password encrypted file without a GUI.
You could use a console-only pinentry, such as pinentry-curses or pinentry-tty. Add the following line in your ~/.gnupg/gpg-agent.conf:
> I have gpg 2.0.14 on CentOS 6.6 and RHEL6U6.
> I've tried to disable pinentry, without success, with the following
> 1. comment out use-agent in ~/.gnupg/gpg.conf
You cannot avoid using GnuPG Agent with gpg 2. As stated in the man page, gpg 2 always requires the agent, and the use-agent option has no effect.
More information about the Gnupg-users