akkoma/config
Oneric 0ec62acb9d Always insert Dedupe upload filter
This actually was already intended before to eradict all future
path-traversal-style exploits and to fix issues with some
characters like akkoma#610 in 0b2ec0ccee. However, Dedupe and
AnonymizeFilename got mixed up. The latter only anonymises the name
in Content-Disposition headers GET parameters (with link_name),
_not_ the upload path.

Even without Dedupe, the upload path is prefixed by an UUID,
so it _should_ already be hard to guess for attackers. But now
we actually can be sure no path shenanigangs occur, uploads
reliably work and save some disk space.

While this makes the final path predictable, this prediction is
not exploitable. Insertion of a back-reference to the upload
itself requires pulling off a successfull preimage attack against
SHA-256, which is deemed infeasible for the foreseeable futures.

Dedupe was already included in the default list in config.exs
since 28cfb2c37a, but this will get overridde by whatever the
config generated by the "pleroma.instance gen" task chose.

Upload+delete tests running in parallel using Dedupe might be flaky, but
this was already true before and needs its own commit to fix eventually.
2024-03-18 22:33:10 -01:00
..
benchmark.exs Support elixir1.15 2023-08-03 17:44:09 +01:00
config.exs Always insert Dedupe upload filter 2024-03-18 22:33:10 -01:00
custom_emoji.txt Ship with hehe 2023-03-27 10:03:12 +01:00
description.exs Sanitise Content-Type of uploads 2024-03-18 22:33:10 -01:00
dev.exs use puts instead warn 2021-07-27 21:01:41 +00:00
docker.exs Docker builds (#231) 2022-10-16 19:25:54 +00:00
dokku.exs Switch from the deprecated "use Mix.config" to "import Config" 2021-05-20 14:02:58 -05:00
prod.exs Switch from the deprecated "use Mix.config" to "import Config" 2021-05-20 14:02:58 -05:00
test.exs Support elixir1.15 2023-08-03 17:44:09 +01:00