summaryrefslogtreecommitdiff
path: root/doc/implementation_notes.md
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor2018-09-05 13:00:28 -0400
committerDaniel Kahn Gillmor2018-09-05 13:00:28 -0400
commit2d9ba81a84a122f09770ed53d8c8284bf3b61dc0 (patch)
treed199b97b6785fbbaf65078a3d50901b4c51c4fab /doc/implementation_notes.md
parent072ee1814d2d40788a93622fe6e753a9f434d515 (diff)
spelling correction.
while mat2 has both a thread model (a thread pool that strips metadata in parallel) and a threat model (a list of malicious adversaries and their capabilities that we are trying to defeat), i think this paragraph is talking about the latter.
Diffstat (limited to '')
-rw-r--r--doc/implementation_notes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/implementation_notes.md b/doc/implementation_notes.md
index 3b8e49d..cbf76ee 100644
--- a/doc/implementation_notes.md
+++ b/doc/implementation_notes.md
@@ -64,7 +64,7 @@ to the filesystem. This ensures that every metadata is removed.
64XML attacks 64XML attacks
65----------- 65-----------
66 66
67Since our thread model conveniently excludes files crafted to specifically 67Since our threat model conveniently excludes files crafted to specifically
68bypass MAT2, fileformats containing harmful XML are out of our scope. 68bypass MAT2, fileformats containing harmful XML are out of our scope.
69But since MAT2 is using [etree](https://docs.python.org/3/library/xml.html#xml-vulnerabilities) 69But since MAT2 is using [etree](https://docs.python.org/3/library/xml.html#xml-vulnerabilities)
70to process XML, it's "only" vulnerable to DoS, and not memory corruption: 70to process XML, it's "only" vulnerable to DoS, and not memory corruption: