** Description changed:
+ [Impact]
+ dirmngr processes are left hanging around
+
+ [Test case]
+ apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092"
< /dev/null ; ps aux
+
+ should not show a dirmngr process after exit (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
** Description changed:
[Impact]
- dirmngr processes are left hanging around
+ 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 ; ps aux
should not show a dirmngr process after exit (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
** Description changed:
[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 ; ps aux
+ 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 after exit (except for any that was
- there before running it, obviously)
+ 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
** Changed in: apt (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
In Progress
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
