{"version":"2.1.232","anchor":"executable-lookalike-filename-checks-harder-to-fool","canonical_anchor":"executable-lookalike-filename-checks-harder-to-fool","heading":"Executable-lookalike filename checks harder to fool","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/executable-lookalike-filename-checks-harder-to-fool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Executable-lookalike filename checks harder to fool\n\nFilenames disguised to mimic existing executables are now much harder to sneak past.\n\n**What**\n\nThe check for filenames that could collide with an existing `.exe` or `.lnk` file now defeats several disguises: characters from the U+F000-U+F0FF private-use block are mapped back to ASCII before comparing, trailing dots and spaces are stripped, and names are compared in both cases rather than lowercased once.\n\n**Details**\n\n- The private-use unmapping step is new in this build.\n\n**Evidence**\n\n`.exe.lnk`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}