{"version":"2.1.238","anchor":"remote-requests-to-change-the-working-directory-reject-netwo","canonical_anchor":"remote-requests-to-change-the-working-directory-reject-netwo","heading":"Remote requests to change the working directory reject network paths","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/remote-requests-to-change-the-working-directory-reject-netwo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Remote requests to change the working directory reject network paths\n\nRemote requests to change your working directory now refuse network paths and hidden-character tricks.\n\n**What**\n\nA request from a remote host to set the working directory is now screened for path shape before anything is resolved, using the same check already applied to remote reads. Paths that resolve to a network location, including obfuscated spellings of one, are refused, as are paths containing invisible characters. The offending path is never repeated back in the response.\n\n**Details**\n\n- Rejections come back with the reason `unsafe_path`.\n- The user-facing text is \"The target is a network path or an obfuscated spelling, which cannot be set as the working directory from a remote host. The path is deliberately not echoed back.\"\n- The existing rejection of paths containing invisible characters is unchanged and also withholds the path.\n- Applies unconditionally on the remote set-working-directory path; there is no setting that turns it off.\n\n**Evidence**\n\n`The target is a network path or an obfuscated spelling, which cannot be set as the working directory from a remote host. The path is deliberately not echoed back.`, `The target resolved to a network path or an obfuscated spelling, which cannot be set as the working directory from a remote host.`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}