[Bug 1634234] Re: apt-key leaves files in /dev open after exit
Scott Moser
smoser at ubuntu.com
Tue Oct 18 01:18:38 UTC 2016
curtin is also busted in cases where the user provides a 'keyid', or
even a 'key' (data inline).
It seems we can/should probably make add_apt_key_raw write data to
/etc/apt/trusted.gpg.d ourselves rather than using apt-key.
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnupg2 in Ubuntu.
https://bugs.launchpad.net/bugs/1634234
Title:
apt-key leaves files in /dev open after exit
Status in apt package in Ubuntu:
New
Status in curtin package in Ubuntu:
New
Status in gnupg2 package in Ubuntu:
New
Bug description:
In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
/dev/urandom open after exiting. Here's a procedure to replicate the
problem:
1. Install Ubuntu 16.10. (I used MAAS for this task.)
2. Install the "lsof" package (which is not installed by default).
3. Type "lsof | grep dev" to see open files.
4. Type "sudo apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 1FEADE10;"
5. Type "lsof | grep dev" again.
6. Compare the output of the two "lsof" commands.
I'm attaching two files, before.txt and after.txt, that show the
before and after results from "lsof | grep dev" in this scenario. Note
that the /dev/null and /dev/urandom files are both open after apt-key
is run, but not before. This problem does NOT occur with Ubuntu 16.04.
This problem is preventing us (the server certification team) from
importing keys in a custom MAAS preseed script; after installing
successfully, umounting the installed image fails because of the open
files on /dev.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634234/+subscriptions
More information about the foundations-bugs
mailing list