<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/cmdline/apt-dump-solver.cc, branch 1.3_rc2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3_rc2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3_rc2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-06-08T15:27:19Z</updated>
<entry>
<title>edsp: drop privileges before executing solvers</title>
<updated>2016-06-08T15:27:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-08T11:44:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=007d8b488787f4c33ced5937f22f99f1b759088a'/>
<id>urn:sha1:007d8b488787f4c33ced5937f22f99f1b759088a</id>
<content type='text'>
Most (if not all) solvers should be able to run perfectly fine without
root privileges as they get the entire state they are supposed to work
on via stdin and do not perform any action directly, but just pass
suggestions on via stdout.

The new default is to run them all as _apt hence, but each solver can
configure another user if it chooses/must. The security benefits are
minimal at best, but it helps preventing silly mistakes (see
35f3ed061f10a25a3fb28bc988fddbb976344c4d) and that is always good.

Note that our 'apt' and 'dump' solver already dropped privileges if they
had them.
</content>
</entry>
<entry>
<title>edsp: optionally store a compressed copy of the last scenario</title>
<updated>2016-06-08T11:07:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-07T15:01:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=385d9f2f23057bc5808b5e013e77ba16d1c94da4'/>
<id>urn:sha1:385d9f2f23057bc5808b5e013e77ba16d1c94da4</id>
<content type='text'>
For bugreports and co it could be handy to have the scenario and all the
settings used in it around later for inspection for EDSP like protocols.
EDSP might not be the most interesting as the user can still interrupt
the process before the solution is applied and users tend to have an
opinion on the "rightness" of a solution, so it is disabled by default.
</content>
</entry>
<entry>
<title>edsp: dump: support dumping into compressed file</title>
<updated>2016-05-20T12:18:36Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-04-27T15:36:07Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=af859f09084b4f6163501f216ba8cc2356fb3f93'/>
<id>urn:sha1:af859f09084b4f6163501f216ba8cc2356fb3f93</id>
<content type='text'>
</content>
</entry>
<entry>
<title>convert EDSP to be based on FileFd instead of FILE*</title>
<updated>2016-05-20T12:18:36Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-04-26T10:26:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ef00bd7af5b2bc0625df58482eacb4c2873c3647'/>
<id>urn:sha1:ef00bd7af5b2bc0625df58482eacb4c2873c3647</id>
<content type='text'>
I doubt there is any non-src:apt usage of these interfaces.
</content>
</entry>
<entry>
<title>wrap every unlink call to check for != /dev/null</title>
<updated>2015-11-04T17:42:28Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-11-02T17:49:52Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ce1f3a2c616b86da657c1c796efa5f4d18c30c39'/>
<id>urn:sha1:ce1f3a2c616b86da657c1c796efa5f4d18c30c39</id>
<content type='text'>
Unlinking /dev/null is bad, we shouldn't do that. Also, we should print
at least a warning if we tried to unlink a file but didn't manage to
pull it of (ignoring the case were the file is /dev/null or doesn't
exist in the first place).

This got triggered by a relatively unlikely to cause problem in
pkgAcquire::Worker::PrepareFiles which would while temporary
uncompressed files (which are set to keep compressed) figure out that to
files are the same and prepare for sharing by deleting them. Bad move.
That also shows why not printing a warning is a bad idea as this hide
the error for in non-root test runs.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>various changes to increase test-coverage</title>
<updated>2015-09-14T13:22:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-12T08:35:49Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7414af7fa88164209eec9c585b8d175c1618ecbc'/>
<id>urn:sha1:7414af7fa88164209eec9c585b8d175c1618ecbc</id>
<content type='text'>
And of course, testing obscure things ends up showing obscure 'bugs' or
better shortcomings/inconsitencies, so lets fix them with the tests.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>fix insecure use of /tmp in EDSP solver 'dump'</title>
<updated>2015-09-14T13:22:18Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-07T17:32:31Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=92b2e38dd1334d7f7a30358124c4fad766ca4666'/>
<id>urn:sha1:92b2e38dd1334d7f7a30358124c4fad766ca4666</id>
<content type='text'>
As said in the bugreport, this is hardly a serious problem on a security
front, but it was always on the list to have the filename configurable
somehow and the stable filename is a problem for parallel executions.

Using an environment variable (APT_EDSP_DUMP_FILENAME) for this is more
or less the best we can do here as solvers do not get told about our
configuration and such.

Closes: 795600
</content>
</entry>
<entry>
<title>stop displaying time of build in online help</title>
<updated>2015-03-16T17:02:08Z</updated>
<author>
<name>Jérémy Bobbio</name>
<email>lunar@debian.org</email>
</author>
<published>2015-03-10T09:09:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=249aec3b7397662a678ea0014f94392085477b09'/>
<id>urn:sha1:249aec3b7397662a678ea0014f94392085477b09</id>
<content type='text'>
As part of the “reproducible builds” effort [1], we have noticed that
apt could not be built reproducibly.

One issue is that it uses the __DATE__ and __TIME__ macros of the C
preprocessor to display the time of build in the online help. We believe
this information not to be really useful to users as they can always
look at the package data and metadata to figure it out.

The attached patch simply removes this information. All
non-documentation packages can then be built reproducibly with our
current experimental framework.

[David: changed the string slightly to be untranslateable as well]

Closes: 774342
</content>
</entry>
<entry>
<title>Rename DropPrivs() to DropPrivileges()</title>
<updated>2014-10-07T11:30:27Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@ubuntu.com</email>
</author>
<published>2014-10-07T11:30:27Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=373fa2b4b2caae977c41b2c10ea27e41308a05c3'/>
<id>urn:sha1:373fa2b4b2caae977c41b2c10ea27e41308a05c3</id>
<content type='text'>
Git-Dch: ignore
</content>
</entry>
<entry>
<title>DropPrivs in the solvers (just to be on the safe side)</title>
<updated>2014-06-11T13:31:38Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@debian.org</email>
</author>
<published>2014-06-11T13:31:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=fc1a78d8e9b958f3d65fe1c03494d785314f9816'/>
<id>urn:sha1:fc1a78d8e9b958f3d65fe1c03494d785314f9816</id>
<content type='text'>
</content>
</entry>
</feed>
