Development record
rm-rf-root-or-home reads a parent segment only at the root: rm -rf ~/../* deletes the home, and rm -rf ~/../../*, $HOME/../../*, /tmp/../* and /etc/../* delete the root, bare and in sh -c, yet each allows, because cleanSeparators takes out only a leading /../ and never folds a .. after a named directory, the home or a tilde. A root or home delete is allowed.
issueresolvedmajoriss-2609290745243990
rm-rf-root-or-home reads a parent segment only at the root: rm -rf ~/../* deletes the home, and rm -rf ~/../../, $HOME/../../, /tmp/../* and /etc/../* delete the root, bare and in sh -c, yet each allows, because cleanSeparators takes out only a leading /../ and never folds a .. after a named directory, the home or a tilde. A root or home delete is allowed.
Grounds
- pursued: every operand beginning at /, ~, $HOME or ${HOME} whose lexical reading is the root, or a directory holding the home globbed or deleted whole, blocks bare and in sh -c and bash -c; a lexical root or home spelling of that shape that still allows would show it wrong
Frontmatter
| id | iss-2609290745243990 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2609290745243990-rm-rf-root-or-home-reads-a-parent.md
open on GitHub ↗ · commit history ↗