Page MenuHome GnuPG

--daemon does not cause gpg-agent to run in the background.
Closed, ResolvedPublic

Description

gpg-agent --daemon

starts the gpg-agent in the foreground on Windows 10.

OS Name Microsoft Windows 10 Pro
Version 10.0.14393 Build 14393

> gpg --version
gpg (GnuPG) 2.1.22
libgcrypt 1.8.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu
This is free software: you are free to change and redis
There is NO WARRANTY, to the extent permitted by law.

Home: C:/Users/user/AppData/Roaming/gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES25
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
> gpg-agent --version
gpg-agent (GnuPG) 2.1.22
libgcrypt 1.8.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu
This is free software: you are free to change and redis
There is NO WARRANTY, to the extent permitted by law.

Event Timeline

justus triaged this task as Wishlist priority.Aug 8 2017, 10:52 AM
justus added a subscriber: justus.

That is correct, gpg-agent does not daemonize on Windows if --daemon is given, it is simply not implemented.

Note that it is usually not required to explicitly start the daemon, and if it is, it can be done using gpgconf --launch gpg-agent.

werner claimed this task.
werner added a subscriber: werner.

In fact, on Windows you would need to have a system service. We did this in the past for the dirmngr but remove that feature due to possible security problems and problems during installation.

To start gpg-agent manually you do what Justus already explained:

gpgconf --launch gpg-agent

The only use case I can see for this is the putty support in gpg-agent.