{"version":"2.1.223","anchor":"stricter-owner-repo-validation-for-gh-commands","canonical_anchor":"stricter-owner-repo-validation-for-gh-commands","heading":"Stricter owner\/repo validation for gh commands","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/stricter-owner-repo-validation-for-gh-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Stricter owner\/repo validation for gh commands\n\nMalformed or sneaky owner\/repo names are rejected before any gh command is built.\n\n**What**\n\nRepository 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.\n\n**Details**\n\n- Each segment must match the allowed character class; segments starting with `-` are rejected outright, as are segments equal to `.` or `..`.\n- Applied when parsing both the `owner\/name` and the `host\/owner\/name` forms.\n- Active for everyone, no gate.\n\n**Evidence**\n\n`protocol.file.allow=never`\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}