Gpg-agent Specific configuration

GPG (GNUPG) tools are widely used, in a previous article on the specific description: http://blog.csdn.net/dongtingzhizi/article/details/26362205, there is a problem worthy of attention, That is, you need to enter password when using GPG private keys. Assuming that only one use once said, only need to enter a password, but assuming the need for bulk use, it is troublesome! Like what. In the recent work. To create a Debian repository, you need to use GPG to sign the Deb package, and thousands of packages are required to enter thousand password. Obviously can't do it. This is the time to use the gpg-agent!

Online about gpg-agent configuration is very few, here is an introduction to the more reliable can participate in:

Https://wiki.archlinux.org/index.php/GnuPG#gpg-agent

Main configuration:

1. Configuration in the startup script (. Profile or ~/.bash_profile):

Eval $ (gpg-agent--daemon) &

2. Configuration in ~/.gnupg/gpg-agent.conf:

Default-cache-ttl 3600   # Password Active time pinentry-program/usr/bin/pinentry-gtk-2   # password Input form program

Also, it is important to note that Gnome-keyring-common takes over the password input (default includes SSH, GPG, etc.) in Ubuntu, and is able to view related files in the/etc/xdg/autostart folder. Assuming that Gpgpassword uses gpg-agent to take over, it is necessary to shield the GPG from the Gnome-keyring-common , which is described in detail in this article:

Https://wiki.archlinux.org/index.php/GnuPG#gpg-agent

actually very easy. Just need to transfer/etc/xdg/autostart/gnome-keyring-gpg.desktop files or link to/dev/null.

Gpg-agent Specific configuration