{"version":"2.1.238","anchor":"sensitive-file-detection-now-sees-through-unicode-look-alike","canonical_anchor":"sensitive-file-detection-now-sees-through-unicode-look-alike","heading":"Sensitive-file detection now sees through Unicode look-alikes","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/sensitive-file-detection-now-sees-through-unicode-look-alike","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Sensitive-file detection now sees through Unicode look-alikes\n\nSensitive filenames disguised with Unicode look-alike letters are now caught.\n\n**What**\n\nA file named with a dotless i, a long s, a Kelvin sign or an ff\/fi ligature no longer slips past the checks that classify a path as sensitive. Paths are normalised through a NFKD plus case round trip with invisible characters stripped, and tracked sensitive files get their own verdict, `sensitive_tracked`. The sync worker's filename-safety checks reject these look-alikes outright.\n\n**Details**\n\n- The set of confusables differs by platform: Windows and WSL use one list, macOS adds \u00df.\n- Runs on every classification, with no flag.\n\n**Evidence**\n\n`sensitive_tracked`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}