sync: auto-sync from GURU-5070 at 2026-07-01 15:49:56
Author: Mike Swanson Machine: GURU-5070 Timestamp: 2026-07-01 15:49:56
This commit is contained in:
@@ -5,6 +5,16 @@ metadata:
|
||||
type: feedback
|
||||
---
|
||||
|
||||
**MECHANICAL FIX FIRST (2026-07-01): for any PowerShell payload crossing a
|
||||
mangling layer (RMM dispatch, ScreenConnect command box, plink, curl.exe args),
|
||||
use `.claude/scripts/ps-encoded.sh`** — it UTF-16LE-base64 encodes a script file
|
||||
and delivers it via `powershell -EncodedCommand` (`encode` prints the paste-safe
|
||||
one-liner; `rmm <agent-uuid> <file>` dispatches + polls via GuruRMM). Base64 has
|
||||
no quotes/backslashes/`$` to strip, so the script arrives byte-exact (verified:
|
||||
UNC `\\` survives). Author the script with the **Write tool**, not a bash heredoc
|
||||
(Git-bash heredocs collapse `\\` even single-quoted). The manual rules below
|
||||
remain for one-off inline args only.
|
||||
|
||||
On Windows, **embedded double-quotes inside a command argument get silently
|
||||
stripped or mangled** at two separate layers we hit repeatedly. The body of the
|
||||
arg survives; the `"` characters vanish, so the receiving program sees broken
|
||||
|
||||
Reference in New Issue
Block a user