Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.1 2015-11-04T17:42:27Z 2015-11-04T17:42:27Z David Kalnischkies david@kalnischkies.de 2015-10-28T13:38:49Z urn:sha1:1dd20368486820efb6ef4476ad739e967174bec4 Based on a discussion with Niels Thykier who asked for Contents-all this implements apt trying for all architecture dependent files to get a file for the architecture all, which is treated internally now as an official architecture which is always around (like native). This way arch:all data can be shared instead of duplicated for each architecture requiring the user to download the same information again and again. There is one problem however: In Debian there is already a binary-all/ Packages file, but the binary-any files still include arch:all packages, so that downloading this file now would be a waste of time, bandwidth and diskspace. We therefore need a way to decide if it makes sense to download the all file for Packages in Debian or not. The obvious answer would be a special flag in the Release file indicating this, which would need to default to 'no' and every reasonable repository would override it to 'yes' in a few years time, but the flag would be there "forever". Looking closer at a Release file we see the field "Architectures", which doesn't include 'all' at the moment. With the idea outlined above that 'all' is a "proper" architecture now, we interpret this field as being authoritative in declaring which architectures are supported by this repository. If it says 'all', apt will try to get all, if not it will be skipped. This gives us another interesting feature: If I configure a source to download armel and mips, but it declares it supports only armel apt will now print a notice saying as much. Previously this was a very cryptic failure. If on the other hand the repository supports mips, too, but for some reason doesn't ship mips packages at the moment, this 'missing' file is silently ignored (= that is the same as the repository including an empty file). The Architectures field isn't mandatory through, so if it isn't there, we assume that every architecture is supported by this repository, which skips the arch:all if not listed in the release file. 2014-10-20T08:37:46Z David Kalnischkies david@kalnischkies.de 2014-10-20T08:23:41Z urn:sha1:4fa34122cbe347d21b3a162ff2fa75dd2e73c3a8 Adds a new testwarning which tests for zero exit and the presents of a warning in the output, failing if either is not the case or if an error is found, too. This allows us to change testsuccess to accept only totally successful executions (= without warnings) which should help finding regressions. Git-Dch: Ignore 2014-10-20T08:37:46Z David Kalnischkies david@kalnischkies.de 2014-10-18T20:46:48Z urn:sha1:846bc058cb0c1bf7ce7c2fb30b9c277e96e9eaf7 Git-Dch: Ignore 2014-10-06T23:59:49Z David Kalnischkies david@kalnischkies.de 2014-10-06T12:29:53Z urn:sha1:5684f71fa0f6c1b765aa53e22ca3b024c578b9c9 Using a different user for calling methods is intended to protect us from methods running amok (via remotely exploited bugs) by limiting what can be done by them. By using root:root for the final directories and just have the files in partial writeable by the methods we enhance this in sofar as a method can't modify already verified data in its parent directory anymore. As a side effect, this also clears most of the problems you could have if the final directories are shared without user-sharing or if these directories disappear as they are now again root owned and only the partial directories contain _apt owned files (usually none if apt isn't running) and the directory itself is autocreated with the right permissions. 2014-10-01T15:13:33Z Michael Vogt mvo@ubuntu.com 2014-10-01T15:13:33Z urn:sha1:0b844e23f014bd3ce95e27fe5fa81138e9ae4879 2014-10-01T11:05:26Z Michael Vogt mvo@ubuntu.com 2014-10-01T10:21:55Z urn:sha1:c99fe2e169243fc6e1a3278ce3768f0f521e260b The configuration key Acquire::AllowInsecureRepositories controls if apt allows loading of unsigned repositories at all. The configuration Acquire::AllowDowngradeToInsecureRepositories controls if a signed repository can ever become unsigned. This should really never be needed but we provide it to avoid having to mess around in /var/lib/apt/lists if there is a use-case for this (which I can't think of right now). 2014-09-29T09:03:02Z Michael Vogt mvo@ubuntu.com 2014-09-29T09:03:02Z urn:sha1:e1bd768b762bd74221f9089133883723a7307f9b 2014-09-26T21:33:57Z Michael Vogt mvo@debian.org 2014-09-26T20:45:18Z urn:sha1:bca84917c326fa3158e120147c8aecebe0789b47 2014-09-23T16:08:53Z Michael Vogt mvo@ubuntu.com 2014-09-23T16:08:53Z urn:sha1:c8aa88aa2c3139584cfabb1ce4619c773e9f2b99 2014-09-16T18:39:13Z Michael Vogt mvo@ubuntu.com 2014-09-16T18:23:43Z urn:sha1:ca7fd76c2f30c100dcf1c12e717ce397cccd690b incorrect invalidating of unauthenticated data (CVE-2014-0488) incorect verification of 304 reply (CVE-2014-0487) incorrect verification of Acquire::Gzip indexes (CVE-2014-0489)