Development record
The guard brief's residual paragraph does not name two postures the exact-shape read of a cat here-document makes sharp: a lone substitution whose output is unknown in command position is an allow by the recorded posture (an allow means no entry matched), and only the exact shape cat <<DELIM, newline, body, delimiter, blanks is read as fixed output, so /bin/cat, command cat, cat -, a redirection after the delimiter word, a backslash-newline before the <<, a command after the document and a backslash-newline after a backtick document all stay unknown and allow (review7-guard finding 4).
The guard brief's residual paragraph does not name two postures the exact-shape read of a cat here-document makes sharp: a lone substitution whose output is unknown in command position is an allow by the recorded posture (an allow means no entry matched), and only the exact shape cat <<DELIM, newline, body, delimiter, blanks is read as fixed output, so /bin/cat, command cat, cat -, a redirection after the delimiter word, a backslash-newline before the <<, a command after the document and a backslash-newline after a backtick document all stay unknown and allow (review7-guard finding 4).
Grounds
- pursued: every shape review7-guard finding 4 lists is named on the four surfaces and pinned at allow; a named shape that no longer allows, or one the review lists that no surface names, would show it wrong
Frontmatter
| id | iss-2609260115383631 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609260115383631-the-guard-brief-does-not-name-the-lone.md
open on GitHub ↗ · commit history ↗