How can you be fooled by the U+202E trick? (2013)

Re:How can you be fooled by the U+202E trick? (2013) by cryptonector on Wednesday February 16, 2022 @01:30AM (#30356952)

There are certainly things that can be done. UTR #36 covers some of the things that can be done.

Besides refusing to render U+202E when it is between characters of scripts that aren't bi-directional and flow in the same direction, the UI could display the string in ways that make it clear (e.g., different color, maybe add a warning tooltip, maybe add a dialog around an operation that could be dangerous, or maybe refuse to perform dangerous operations).

[ Parent | on HN ]

Re:How can you be fooled by the U+202E trick? (2013) by account42 on Wednesday February 16, 2022 @09:50AM (#30360651)

Another option for filenames would be to recognize that the basename and extensions are distinct parts and the extension should always be displayed after the basename no matter what is in the basename. Of course, this adds lots of complexity so ¯\_(ツ)_/¯

[ Parent | on HN ]

Re:How can you be fooled by the U+202E trick? (2013) by cryptonector on Wednesday February 16, 2022 @10:21AM (#30361076)

Problem is that there's cases like foo.tar.gz. What's the extension there?

[ Parent | on HN ]