You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(security): escape rejected names in CLI validation diagnostics
The CLI name validators echoed rejected input verbatim, so a name carrying
ANSI escape or control bytes reached the terminal and CI logs unchanged. Reuse
the canonical bounded ASCII preview already applied to blueprint names.
Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Copy file name to clipboardExpand all lines: docs/reference/troubleshooting.mdx
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -663,6 +663,9 @@ Sandbox names must be lowercase, start with a letter, contain only letters, numb
663
663
The CLI rejects names that do not match these rules.
664
664
It prints a `Try: <suggested-slug>` recovery line whenever it can derive a valid lowercase, hyphen-separated form from the input, so passing `--name MyAssistant` reports `Try: myassistant` and you can rerun with the suggested slug.
665
665
666
+
The error repeats the rejected value as a quoted preview rather than the raw input.
667
+
Characters outside printable ASCII appear as `\uXXXX` escapes and the preview stops after 80 characters, so a name that carries control or escape sequences cannot change your terminal or a CI log.
668
+
666
669
Names that collide with global CLI commands are also rejected.
667
670
Reserved names include `onboard`, `list`, `deploy`, `setup`, `start`, `stop`, `status`, `debug`, `uninstall`, `credentials`, and `help`.
668
671
Using a reserved name would cause the CLI to route to the global command instead of the sandbox.
0 commit comments