summaryrefslogtreecommitdiff
path: root/test/integration/test-unpack-different-version-unpacked
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2016-07-27 15:52:22 +0200
committerDavid Kalnischkies <david@kalnischkies.de>2016-07-27 15:52:22 +0200
commit0e071dfe205ad21d8b929b4bb8164b008dc7c474 (patch)
tree5b5c0aac4f4e8745872775fcceb1422d96edaf3f /test/integration/test-unpack-different-version-unpacked
parent353b7bab08704cd2f7e2b6951c9dcd7cf3023e3a (diff)
rred: truncate result file before writing to it
If another file in the transaction fails and hence dooms the transaction we can end in a situation in which a -patched file (= rred writes the result of the patching to it) remains in the partial/ directory. The next apt call will perform the rred patching again and write its result again to the -patched file, but instead of starting with an empty file as intended it will override the content previously in the file which has the same result if the new content happens to be longer than the old content, but if it isn't parts of the old content remain in the file which will pass verification as the new content written to it matches the hashes and if the entire transaction passes the file will be moved the lists/ directory where it might or might not trigger errors depending on if the old content which remained forms a valid file together with the new content. This has no real security implications as no untrusted data is involved: The old content consists of a base file which passed verification and a bunch of patches which all passed multiple verifications as well, so the old content isn't controllable by an attacker and the new one isn't either (as the new content alone passes verification). So the best an attacker can do is letting the user run into the same issue as in the report. Closes: #831762
Diffstat (limited to 'test/integration/test-unpack-different-version-unpacked')
0 files changed, 0 insertions, 0 deletions