Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

persisting gpg-agent keeps cmd batch windows open #56

Open
LigH-de opened this issue Oct 8, 2018 · 1 comment
Open

persisting gpg-agent keeps cmd batch windows open #56

LigH-de opened this issue Oct 8, 2018 · 1 comment

Comments

@LigH-de
Copy link

LigH-de commented Oct 8, 2018

Please excuse if the location for this issue is wrong; but it seemed to be the most specific project's tracker to me.

When pacman-key is used in a Windows batch, a process of pgp-agent spawns. According to IRC #gnupg, this is automatic and can't be disabled in a gpg.conf anymore in GnuPG v2.

As long as this process is alive, the cmd window running the batch file (specifically, MABS) will not close when the batch finishes.

I tried to kill this agent at the end of the batch, using the following command:

gpg-connect-agent -q killagent /bye

This prints as result:

OK connection closed

but the process 'gpg-agent.exe' persists. Current workaround:

taskkill /IM gpg-agent.exe /f

at the end of the batch.

May this be an MSYS2 or more generally GnuPG Windows build specific issue in a way that gpg-connect-agent tries to kill the gpg-agent process with a method that doesn't work reliably in Windows?

@JayFoxRox
Copy link

This affects us on Travis CI, and seems to have changed very recently: XboxDev/nxdk#218

Does anybody know when / where / why this changed?
Can we remove the taskkill altogether?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants