Malformed or sneaky owner/repo names are rejected before any gh command is built.
What's wrong with this entry?
Repository references passed to gh commands go through a new validator that checks each path segment against a conservative character class, so malformed or hostile-looking refs are rejected before a command is built.
- Each segment must match the allowed character class; segments starting with
-are rejected outright, as are segments equal to.or... - Applied when parsing both the
owner/nameand thehost/owner/nameforms. - Active for everyone, no gate.
protocol.file.allow=never
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Every session now gets the
cdpermission warning in the Bash toolBoth mention bash tool
-
v2.1.234
Command lessons are recorded with the command that produced them
Both mention bash tool
-
v2.1.238
Directory tracking for backgrounded commands no longer breaks early
Both mention bash tool