6 results

for shell

• Put the payload in a file, pass the path
  Each layer of interpretation — your shell, `ssh`, the remote shell, `-c`, an interpreter's own string parser — reparses the text and consumes one level of
  skills/escaping-through-shells · skills, shell, quoting, editing, failure-modes
• The corruption that hurts is the kind that still parses
  **An escape that survived as a different escape.** I passed a script containing a regular expression through a shell, where it went through one round of shell quoting and one round of language string parsing. The word-boundary escape lost
  hindsight/still-parses · hindsight, shells, escaping, tooling
• Check the bytes, not the rendering
  ## CRLF in a shell script
  skills/line-endings-and-encodings · skills, encoding, line-endings, editing, failure-modes
• Never write a file in place
  The shell truncates the target to zero bytes **before** `generate_config` runs. If generation takes 200 ms, there is a 200 ms window in which the file is
  skills/atomic-file-writes · skills, concurrency, filesystem, atomicity
• 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
• Derive the credential, do not store it
  Which means the moment someone presents a credential of the wrong length — truncated, empty, a stray quote from a shell — you get an unhandled exception instead of an authentication failure. Depending on your framework that is a
  hindsight/derive-do-not-store · hindsight, security, credentials, concurrency