apt/apt-pkg/metaindex.h, branch 2.3.0Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.3.02020-02-26T19:34:54Zapt-pkg: default visibility to hidden2020-02-26T19:34:54ZJulian Andres Klodejulian.klode@canonical.com2019-08-13T17:15:19Zurn:sha1:db678df196ccd8f9f6fb336706cf5701d1e53aa6Make metaIndex::GetNotBefore virtual2020-02-26T13:32:36ZJulian Andres Klodejulian.klode@canonical.com2020-02-26T13:32:36Zurn:sha1:43b418a68d8e64b4f0220e730ccf7441e2796ea6metaindex: Add Origin, Label, Version, DefaultPin, ReleaseNotes members2020-02-26T13:19:10ZJulian Andres Klodejulian.klode@canonical.com2020-02-26T13:19:10Zurn:sha1:d77c1c7db760ae21d703b8b0f129379e54918bf7
These were hidden behind the d-pointer previously.
Remove various dynamic_cast uses, use virtual methods instead2020-02-26T13:16:17ZJulian Andres Klodejulian.klode@canonical.com2020-02-26T13:15:24Zurn:sha1:d31f807a8d3f031d5efc5c3be9b76f9a9ac22d5dRun unifdef -DAPT_{8,9,10,15}_CLEANER_HEADERS2019-06-12T13:02:55ZJulian Andres Klodejulian.klode@canonical.com2019-05-11T15:17:20Zurn:sha1:daa1352ed3d2bb4bc6aa0f0e7f22be3f0908942dmetaindex: Remove deprecated checkSum::Hash (replaced by Hashes)2019-02-26T15:31:20ZJulian Andres Klodejulian.klode@canonical.com2019-02-26T11:53:04Zurn:sha1:97bd7e492bad1ef50f2659faef61b409ffe67311Check that Date of Release file is not in the future2018-02-19T15:05:01ZJulian Andres Klodejulian.klode@canonical.com2018-01-29T15:15:41Zurn:sha1:9e5899cac1a6367e3769af52a724821880e538f6
By restricting the Date field to be in the past, an attacker cannot
just create a repository from the future that would be accepted as
a valid update for a repository.
This check can be disabled by Acquire::Check-Date set to false. This
will also disable Check-Valid-Until and any future date related checking,
if any - the option means: "my computers date cannot be trusted."
Modify the tests to allow repositories to be up to 10 hours in the
future, so we can keep using hours there to simulate time changes.
Reformat and sort all includes with clang-format2017-07-12T11:57:51ZJulian Andres Klodejak@debian.org2017-07-12T11:40:41Zurn:sha1:87274d0f22e1dfd99b2e5200e2fe75c1b804eac3
This makes it easier to see which headers includes what.
The changes were done by running
git grep -l '#\s*include' \
| grep -E '.(cc|h)$' \
| xargs sed -i -E 's/(^\s*)#(\s*)include/\1#\2 include/'
To modify all include lines by adding a space, and then running
./git-clang-format.sh.
show a Release-Notes URI if infos were changed2017-06-28T17:18:47ZDavid Kalnischkiesdavid@kalnischkies.de2017-05-28T11:24:33Zurn:sha1:96ebab48c25fcd1ee83729cdba4be8a6343a8766
This gives the repository owner a chance to explain why this change was
needed – e.g. explaining the organisational changes or simply detailing
the changes in the new release made. Note that this URI is also shown
if the change is accepted, so it also draws attention to release notes
of minor updates (if users watch apt output closely).
error in update on Release information changes2017-06-28T17:18:47ZDavid Kalnischkiesdavid@kalnischkies.de2017-04-12T15:39:06Zurn:sha1:081fbea14d12f79c8d91ce4fe1f1004c7bc08656
The value of Origin, Label, Codename and co can be used in user
configuration from apts own pinning to unattended upgrades.
A repository changing this values can therefore have serious effects on
the behaviour of apt and other tools using these values.
In a first step we will generate error messages for these changes now
explaining the need for explicit confirmation and provide config options
and commandline flags to accept them.