{"version":"2.1.224","anchor":"linux-sandbox-violations-show-the-real-command","canonical_anchor":"linux-sandbox-violations-show-the-real-command","heading":"Linux sandbox violations show the real command","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/linux-sandbox-violations-show-the-real-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Linux sandbox violations show the real command\n\nLinux sandbox violations now show the real command, so ignoreViolations patterns match what you wrote.\n\n**What**\n\nRecords of blocked syscalls in the Linux sandbox now carry the actual command text rather than an opaque internal id, using the same lookup macOS already used. This also means `ignoreViolations` patterns match against the command you wrote.\n\n**Evidence**\n\n`resolveCommandText`\n\n- Area: Sandbox\n- Names: `ignoreViolations`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}