<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/contrib, branch 1.1.exp13</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.1.exp13</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.1.exp13'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2015-09-14T13:22:18Z</updated>
<entry>
<title>srv test: do 100 pulls twice and compare list</title>
<updated>2015-09-14T13:22:18Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-11T23:23:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9bfb1136abfd58e48545304507dedceb2fe87a36'/>
<id>urn:sha1:9bfb1136abfd58e48545304507dedceb2fe87a36</id>
<content type='text'>
The previous implementation was still a bit unstable in terms of failing
at times. Lets try if we have more luck with this one.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>avoid using global PendingError to avoid failing too often too soon</title>
<updated>2015-09-14T13:22:18Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-10T17:00:51Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=95278287f4e1eeaf5d96749d6fc9bfc53fb400d0'/>
<id>urn:sha1:95278287f4e1eeaf5d96749d6fc9bfc53fb400d0</id>
<content type='text'>
Our error reporting is historically grown into some kind of mess.
A while ago I implemented stacking for the global error which is used in
this commit now to wrap calls to functions which do not report (all)
errors via return, so that only failures in those calls cause a failure
to propergate down the chain rather than failing if anything
(potentially totally unrelated) has failed at some point in the past.

This way we can avoid stopping the entire acquire process just because a
single source produced an error for example. It also means that after
the acquire process the cache is generated – even if the acquire
process had failures – as we still have the old good data around we can and
should generate a cache for (again).

There are probably more instances of this hiding, but all these looked
like the easiest to work with and fix with reasonable (aka net-positive)
effects.
</content>
</entry>
<entry>
<title>copy ReadWrite-error to the bottom to make clang happy</title>
<updated>2015-09-14T13:22:18Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-07T19:14:55Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8f5b67ae1488f5addc70b337aea7aa1ced168550'/>
<id>urn:sha1:8f5b67ae1488f5addc70b337aea7aa1ced168550</id>
<content type='text'>
clang detects that fd isn't set in the ReadWrite case – just that this
is supposed to be catched earlier in this method already, but it doesn't
hurt to make it explicit here as well and clang is happy, too.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>implement CopyFile without using FileFd::Size()</title>
<updated>2015-09-14T13:22:18Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-07T17:10:21Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e977b8b9234ac5db32f2f0ad7e183139b988340d'/>
<id>urn:sha1:e977b8b9234ac5db32f2f0ad7e183139b988340d</id>
<content type='text'>
Pipes and such have no good Size value, but we still want to copy from
it maybe and we don't really need size as we can just as well read as
long as we get data out of a file to copy it.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>avoid triggering the c++11 erase api change on travis</title>
<updated>2015-09-02T10:35:22Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-02T10:35:22Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c7609dd7a418428ffbca4c81a7950c4f53c92450'/>
<id>urn:sha1:c7609dd7a418428ffbca4c81a7950c4f53c92450</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>use clock() as source for SRV randomness</title>
<updated>2015-09-01T17:01:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-01T16:32:22Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=76abe9a5aad69eb7e67295588c6825cdae0341af'/>
<id>urn:sha1:76abe9a5aad69eb7e67295588c6825cdae0341af</id>
<content type='text'>
Initializing a random number generator with the time since epoch could
be good enough, but reaches its limits in test code as the 100
iterations might very well happen in the same second and hence the seed
number is always the same… clock() has a way lower resolution so it
changes more often and not unimportant: If many users start the update
at the same time it isn't to unlikely the SRV record will be ordered in
the same second choosing the same for them all, but it seems less likely
that the exact same clock() time has passed for them.

And if I have to touch this, lets change a few other things as well to
make me and/or compilers a bit happier (clang complained about the usage
of a GNU extension in the testcase for example).
</content>
</entry>
<entry>
<title>use unusable-for-security hashes for integrity checks</title>
<updated>2015-09-01T12:19:44Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-01T11:58:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=63d609985eb7eefa5f2332bfe4fab96f017760a1'/>
<id>urn:sha1:63d609985eb7eefa5f2332bfe4fab96f017760a1</id>
<content type='text'>
We want to declare some hashes as not enough for security, so that a
user will need --allow-unauthenticated or similar to get data secured
only by those hashes, but we can still us these hashes for integrity
checks if we got them.
</content>
</entry>
<entry>
<title>Consider md5sum no longer a usable hash</title>
<updated>2015-09-01T09:29:49Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@ubuntu.com</email>
</author>
<published>2015-09-01T09:13:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=55ae7a516126f9f064d8353bf962256b7307590a'/>
<id>urn:sha1:55ae7a516126f9f064d8353bf962256b7307590a</id>
<content type='text'>
The md5sum hash is broken since some time and we should no longer
consider it a usable hash. Also update the tests to reflect this.
</content>
</entry>
<entry>
<title>improve CheckDropPrivsMustBeDisabled further</title>
<updated>2015-09-01T00:49:53Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-01T00:29:27Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=226c0f64d46019d675840b16bd44ff985b45ad0f'/>
<id>urn:sha1:226c0f64d46019d675840b16bd44ff985b45ad0f</id>
<content type='text'>
Various smaller improvements so that the check deals better with already
downloaded files, relative paths and other things.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>ignore for _apt inaccessible TMPDIR in pkgAcqChangelog</title>
<updated>2015-08-31T00:31:10Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-08-31T00:31:10Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=dd6da7d2392e2ad35c444ebc2d7bc2308380530c'/>
<id>urn:sha1:dd6da7d2392e2ad35c444ebc2d7bc2308380530c</id>
<content type='text'>
Using libpam-tmpdir caused us to create our download tmp directory in
root's private tmp before changing to _apt, which wouldn't have access
to it.

By extending our GetTempDir method with an optional wrapper changing the
effective user, we can test if a given user can access the directory and
ignore TMPDIR if not instead of ignoring TMPDIR completely.

Closes: 797270
</content>
</entry>
</feed>
