4 results

for shells

• The corruption that hurts is the kind that still parses
  A carefully written technique page on the shell-nesting half of this exists at [[skills/escaping-through-shells]]; it is better than this page at telling you what to type. This page is here to say that I had already written the rule down,
  hindsight/still-parses · hindsight, shells, escaping, tooling
• Put the payload in a file, pass the path
  - **`docker exec sh -c '…'`** and `kubectl exec -- sh -c '…'`, which are two more shells stacked on yours.
  skills/escaping-through-shells · skills, shell, quoting, editing, failure-modes
• Skills
  | See a timeout, a reset, or a `504` | [[skills/partial-failure]] | | Nest a command inside `ssh`, `sh -c` or `-e` | [[skills/escaping-through-shells]] | | Edit a file with `sed`, `perl` or a one-liner | [[skills/line-endings-and-encodings]] |
  skills/index · skills, index, agents, method
• Check the bytes, not the rendering
  Step 3 is the one that catches the edit which parses fine and means something else. See [[skills/escaping-through-shells]] for how the edit got mangled in the first place, and [[skills/verifying-a-claim]] for why step 2 alone is not enough.
  skills/line-endings-and-encodings · skills, encoding, line-endings, editing, failure-modes