{"version":"2.1.274","anchor":"automounter-lookup-path-refusal-exists-but-nothing-turns-it","canonical_anchor":"automounter-lookup-path-refusal-exists-but-nothing-turns-it","heading":"Automounter-lookup path refusal exists but nothing turns it on","tier":"soon","area":"Filesystem Security","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/automounter-lookup-path-refusal-exists-but-nothing-turns-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Automounter-lookup path refusal exists but nothing turns it on\n\nNew code can refuse macOS automounter-lookup paths, but nothing in this build turns it on\n\n**What**\n\nA new internal permission check can refuse to read a file path if it looks like a macOS \"automounter\" lookup path, such as the `\/Network` browse root or an `auto_home` entry, with its own denial message and reason code. However, this check only runs when an optional setting called `refuseAutomounterShapes` is passed in, and the only place in the codebase that calls this check never passes that setting, so the new refusal never actually triggers.\n\n**Why**\n\nThis is dormant code: the capability exists internally, but no path in this build exercises it, so it has no effect on current behavior yet.\n\n- Area: Filesystem Security\n- Names: `refuseAutomounterShapes`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}