summaryrefslogtreecommitdiff
path: root/test/integration/test-multiarch-foreign
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2019-01-28 20:45:02 +0100
committerDavid Kalnischkies <david@kalnischkies.de>2019-01-28 20:45:02 +0100
commit9b840b59cc80a072e14b8adc9d76669a7a50ab87 (patch)
treea3ceb1afc6921c519a33dc35b2bfa6214bd0f363 /test/integration/test-multiarch-foreign
parent93c9a49c1fd378cd0a3b472d68afb3378da145b8 (diff)
Refuse files with lines unexpectedly starting with a dash
We support dash-encoding even if we don't really work with files who would need it as implementations are free to encode every line, but otherwise a line starting with a dash must either be a header we parse explicitly or the file is refused. This is against the RFC which says clients should warn on such files, but given that we aren't expecting any files with dash-started lines to begin with this looks a lot like a we should not continue to touch the file as it smells like an attempt to confuse different parsers by "hiding" headers in-between others. The other slightly more reasonable explanation would be an armor header key starting with a dash, but no existing key does that and it seems unlikely that this could ever happen. Also, it is recommended that clients warn about unknown keys, so new appearance is limited.
Diffstat (limited to 'test/integration/test-multiarch-foreign')
0 files changed, 0 insertions, 0 deletions