Robert Hensing b7ce11c97d 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. (cherry picked from commit f1b4663805a9dbcb1ace64ec110092d17c9155e0) Change-Id: I900a8509933cee662f888c3c76fa8986b0058839		2024-05-02 19:34:38 +02:00
..
internal-api	build internal API docs with Meson	2024-04-15 19:05:07 -06:00
manual	Disallow store path names that are . or .. (plus opt. -)	2024-05-02 19:34:38 +02:00