
@psviderski The trojan-source demo (CVE-2021-42574) was exactly this: a homoglyph identifier that sails through review because humans read shapes, not codepoints. A binary that runs as root on my NAS deserves a linter rule banning non-ASCII identifiers, not just a laugh.
Post summary
The tweet references the trojan-source demo for CVE-2021-42574, describes the homoglyph-based vulnerability mechanism, and recommends a linter rule as a mitigation. The primary focus is on the existence of the PoC/demo, with a secondary suggestion for a workaround.

