[Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.6.2

---------------
apt (1.6.2) unstable; urgency=medium

  * Fix build with new gtest (Closes: #897149)
  * Handle a missed case of timed out ip addresses (LP: #1766542)
  * Lower default network timeouts from 120s to 30s
  * apt-key: Pass all instead of gpg-agent to gpgconf --kill (LP: #1773992)
  * Fix lock counting in debSystem (LP: #1778547)
  * CI fixes:
   - tests: Do not expect requested-by if sudo was invoked by root
   - Run tests on GitLab CI
   - CI: Export DEBIAN_FRONTEND=noninteractive in all CI environments

 -- Julian Andres Klode <juliank at ubuntu.com>  Mon, 25 Jun 2018 17:15:10
+0200

** Changed in: apt (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1773992

Title:
  apt-key adv should gpgconf --kill all the things after execution

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  dirmngr processes are left hanging around after doing key server stuff with apt-key adv.

  [Test case]
  apt-key adv --recv-keys "8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092" < /dev/null ; sleep 2; ps aux

  should not show a dirmngr process (except for any that was there
  before running it, obviously).

  [Regression potential]
  This just kills more processes using the temporary gpg home directory. It's hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill the wrong process, who knows?

  [Original bug report]
  apt-key adv should gpgconf --kill all the things after execution

  to ensure that e.g. dirmngr processes are not left hanging around

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1773992/+subscriptions