{"version":"2.1.281","anchor":"chrome-file-upload-refuses-paths-whose-symlink-ancestry-cann","canonical_anchor":"chrome-file-upload-refuses-paths-whose-symlink-ancestry-cann","heading":"Chrome file upload refuses paths whose symlink ancestry cannot be vetted","tier":"notice","area":"Chrome","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/chrome-file-upload-refuses-paths-whose-symlink-ancestry-cann","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Chrome file upload refuses paths whose symlink ancestry cannot be vetted\n\nClaude in Chrome file upload now refuses a path it cannot vet because of a symlink chain or an unreadable part\n\n**What**\n\nClaude in Chrome can upload files from your computer to a web page. It now checks a file's path before touching the file itself. It refuses the upload if the path goes through a chain of symbolic links, or if some part of the path cannot be read. A symbolic link, or symlink, is a file that points to another location. The refusal reads \"path could not be vetted (symbolic link chain or unreadable component)\".\n\n**Why**\n\nA symlink can make a harmless-looking path lead to a different file. Refusing paths that cannot be fully checked stops the upload from sending a file you did not mean to share. If an upload is refused, give the real file location instead of a linked one.\n\n- Area: Chrome\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}