DarkPlayer@lemmy.world to Programming@programming.dev · 10 months agoUnicode tricks in pull requests: Do review tools warn us?semanticdiff.comexternal-linkmessage-square6fedilinkarrow-up12arrow-down10cross-posted to: security@lemmy.ml
arrow-up12arrow-down1external-linkUnicode tricks in pull requests: Do review tools warn us?semanticdiff.comDarkPlayer@lemmy.world to Programming@programming.dev · 10 months agomessage-square6fedilinkcross-posted to: security@lemmy.ml
minus-squaremonk@lemmy.unboiled.infolinkfedilinkarrow-up2·10 months agoHomoglyphs? Invisible text? Bidirectional text? Just highlight every line that goes beyond ASCII with yellow warning colors and require to vet it. Maybe make localization data an exception.
minus-squarearthur@lemmy.ziplinkfedilinkEnglisharrow-up1·10 months agoOr the non-ascii character itself.
minus-squaremonk@lemmy.unboiled.infolinkfedilinkarrow-up1·10 months agoDoesn’t work if it’s invisible.
minus-squareActual@programming.devlinkfedilinkEnglisharrow-up1·10 months agoVery simple solution actually. Here I was thinking we’d need AI to solve it.
minus-squareDudeDudenson@lemmings.worldlinkfedilinkarrow-up4·10 months agoPeople would call that solution AI these days. If it has at least one if statement then they call it AI
Homoglyphs? Invisible text? Bidirectional text? Just highlight every line that goes beyond ASCII with yellow warning colors and require to vet it. Maybe make localization data an exception.
Or the non-ascii character itself.
Doesn’t work if it’s invisible.
Very simple solution actually. Here I was thinking we’d need AI to solve it.
People would call that solution AI these days. If it has at least one if statement then they call it AI