{"version":"2.1.251","anchor":"plugin-symlinks-from-command-produced-directories-are-now-ve","canonical_anchor":"plugin-symlinks-from-command-produced-directories-are-now-ve","heading":"Plugin symlinks from command-produced directories are now vetted","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/plugin-symlinks-from-command-produced-directories-are-now-ve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Plugin symlinks from command-produced directories are now vetted\n\nSymlinks inside a command-produced plugin directory are now checked before being installed.\n\n**What**\n\nWhen a plugin install produces a directory whose top-level entries are symlinks, each entry is now run through the same untrusted-link check already used elsewhere, so a link pointing at a network location or through an untrusted link is refused instead of being linked into the install.\n\n**Details**\n\n- The refusal message names the path and the reason.\n- Unconditional.\n\n**Evidence**\n\n`points at a network location or through a link that cannot be trusted; refusing to link it`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}