apt/test/integration/test-releasefile-verification, branch 1.1.exp1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.exp12013-11-30T11:38:26Ztests: add a webserverconfig method to abstract config2013-11-30T11:38:26ZDavid Kalnischkieskalnischkies@gmail.com2013-10-23T14:32:48Zurn:sha1:f2c0ec8bdb00b44de240190dae39fa255b6c85de
The URI to use to set a config option is a bit arcane to write/remember
and checking if the setting was successful doubly so.
Git-Dch: Ignore
retry without partial data after a 416 response2013-10-01T09:04:14ZDavid Kalnischkieskalnischkies@gmail.com2013-09-16T21:21:11Zurn:sha1:331e8396ee5a4f2e7d276eddc54749b2a13dd789
If we get a 416 from the server it means the Range we asked for is above
the real filesize of the file on the server. Mostly this happens if the
server isn't supporting If-Range, but regardless of how we end up with
the partial data, the data is invalid so we discard it and retry with a
fresh plate and hope for the best.
Old behavior was to consider 416 an error and retry with a different
compression until we ran out of compression and requested the
uncompressed file (which doesn't exist on most mirrors) with an accept
line which server answered with "406 Not Acceptable".
Closes: 710924
configurable compression for testcases2013-08-27T22:24:32ZDavid Kalnischkieskalnischkies@gmail.com2013-08-27T22:24:32Zurn:sha1:276e51dd701590d187ca2999722329518af96121
Compressing files in 4 different styles eats test-time for no practical
gain if we don't test them explicitly, so default to just building 'gz'
compressed files as it is the simplest compression algorithm supported
Git-Dch: Ignore
test Release file handling with expired keys2013-08-12T16:01:37ZDavid Kalnischkieskalnischkies@gmail.com2013-08-09T20:20:27Zurn:sha1:29a59c460403820d0f039398194e321b7e0921fc
Signing files with expired keys is not as easy as it sounds, so the
framework jumps a few loops to do it, but it might come in handy to have
an expired key around for later tests even if it is not that different
from having no key in regards to APT behaviour.
Git-Dch: Ignore
simple fork and pidfile aptwebserver2013-06-24T15:01:33ZDavid Kalnischkieskalnischkies@gmail.com2013-06-24T14:34:38Zurn:sha1:e3c62328abbd548bb0da42fdbad954b3ce4f7102
Forking only after being ready to accept clients avoids running races
with the tests which sometimes failed on the first 'apt-get update'
(or similar) with the previous background-start and hope for the best…
The commit fixes also some oversight output-order changes in regards to
Description-md5 and (I-M-S) race conditions in various tests.
Git-Dch: Ignore
merged patch from Daniel Hartwig to fix URI and proxy releated issues2013-05-08T15:50:15ZMichael Vogtmichael.vogt@ubuntu.com2013-05-08T15:50:15Zurn:sha1:5b63d2a9a2e088bb7df7c703e9452af7efc88210* SECURITY UPDATE: InRelease verification bypass2013-03-14T13:26:43ZMichael Vogtegon@debian-devbox2013-03-14T13:26:43Zurn:sha1:55971004215609a02ca19c59bd058da20729ba11
- CVE-2013-1051
* apt-pkg/deb/debmetaindex.cc,
test/integration/test-bug-595691-empty-and-broken-archive-files,
test/integration/test-releasefile-verification:
- disable InRelease downloading until the verification issue is
fixed, thanks to Ansgar Burchardt for finding the flawfix the remaining lzma calls with xz --format=lzma in the testcases2012-04-11T10:36:32ZDavid Kalnischkieskalnischkies@gmail.com2012-04-11T10:36:32Zurn:sha1:3b4d8136e78b9f2a70431ece4c850861d90e8bb1testcase for CVE-2012-02142012-03-03T10:44:06ZSimon Ruderichsimon@ruderich.org2012-03-03T10:44:06Zurn:sha1:43c1ca5d1eb8101e3a52d19a2175c14817e6dd14remove the caches in 'apt-get update', too, as they will be2011-08-22T21:10:15ZDavid Kalnischkieskalnischkies@gmail.com2011-08-22T21:10:15Zurn:sha1:8de79b68a834a6cc7abb8976e96ed19374fc02a2
invalid in most cases anyway