diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2016-01-27 15:28:17 +0100 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2016-01-27 16:39:52 +0100 |
| commit | 6fc2e03084c7e027c2b9a63c1fe99ff743aae3b6 (patch) | |
| tree | 05128f88da578c7b0255663c30bb85140634bd9a /test/integration/framework | |
| parent | a133f79c8766aee5b7d7811285e60b3d311d8473 (diff) | |
only warn about missing/invalid Date field for now
The Date field in the Release file is useful to avoid allowing an
attacker to 'downgrade' a user to earlier Release files (and hence to
older states of the archieve with open security bugs). It is also needed
to allow a user to define min/max values for the validation of a Release
file (with or without the Release file providing a Valid-Until field).
APT wasn't formally requiring this field before through and (agrueable
not binding and still incomplete) online documentation declares it
optional (until now), so we downgrade the error to a warning for now to
give repository creators a bit more time to adapt – the bigger ones
should have a Date field for years already, so the effected group should
be small in any case.
It should be noted that earlier apt versions had this as an error
already, but only showed it if a Valid-Until field was present (or the
user tried to used the configuration items for min/max valid-until).
Closes: 809329
Diffstat (limited to 'test/integration/framework')
| -rw-r--r-- | test/integration/framework | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/test/integration/framework b/test/integration/framework index b0be3eaf1..2aed77d5b 100644 --- a/test/integration/framework +++ b/test/integration/framework @@ -1522,6 +1522,14 @@ msgfailoutput() { msgfailoutputstatfile "$2" "$3" done echo '#### test output ####' + elif [ "$1" = 'cmp' ]; then + echo >&2 + while [ -n "$2" ]; do + echo "#### Complete file: $2 ####" + cat >&2 "$2" || true + shift + done + echo '#### cmp output ####' fi cat >&2 "$OUTPUT" msgfail "$MSG" |