Robert Hensing 6e3548f866 Disallow store path names that are . or .. (plus opt. -) ... As discussed in the maintainer meeting on 2024-01-29. Mainly this is to avoid a situation where the name is parsed and treated as a file name, mostly to protect users. .-* and ..-* are also considered invalid because they might strip on that separator to remove versions. Doesn't really work, but that's what we decided, and I won't argue with it, because .-* probably doesn't seem to have a real world application anyway. We do still permit a 1-character name that's just "-", which still poses a similar risk in such a situation. We can't start disallowing trailing -, because a non-zero number of users will need it and we've seen how annoying and painful such a change is. What matters most is preventing a situation where . or .. can be injected, and to just get this done.		2024-03-26 13:47:41 +01:00
..
test-data	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00
derivation.cc	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00
derived-path.cc	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00
downstream-placeholder.cc	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00
local.mk	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00
machines.cc	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00
nar-info-disk-cache.cc	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00
outputs-spec.cc	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00
path.cc	Disallow store path names that are . or .. (plus opt. -)	2024-03-26 13:47:41 +01:00
references.cc	Move tests to separate directories, and document	2023-12-01 13:05:03 -05:00