3 ms·
The biggest actual problem is Greek vs Cyrillic. They appear the same, but use different encodings. Any filename (directory entry as identifier) must forbid mix
by rurban 9y ago
The biggest actual problem is Greek vs Cyrillic. They appear the same, but use different encodings. Any filename (directory entry as identifier) must forbid mixed scripts. See TR31 http://www.unicode.org/reports/tr31/ http://www.unicode.org/reports/tr31/
Combining marks or RTL switching tricks are the other popular spoofs.
- cryptonector 9y agoConfusables are a real problem. Some Cyrillic and Greek letters even look like Latin letters. And in some fonts '1' (one) and 'l' (ell) look the same even in Latin. Dealing with these is much harder than with normalization forms. And confusables are a source of serious security headaches.
- Piskvorrr 9y ago1Il|!
- kps 9y ago> Any filename (directory entry as identifier) must forbid mixed scripts. So I'm not allowed to name my files “A=πr²” or “10kΩ Резисторы”?
- rurban 9y agoAccording to me not if you mixed Greek with Cyrillic, and not Math with Cyrillic. Unfortunately nobody cares about Unicode identifier security models. Garbage out is the most popular ideology.
- kps 9y agoI take the view that modern file names are human readable labels, not access keys. “10kΩ Резисторы” is Cyrillic, Latin, and Greek (U+2126 canonically maps to U+03A9). A proposal that disallows that but allows “10kΩ Resistors” is a political non-starter.
- rurban 9y agoThe Unicode consortium has published recommendations with various security levels everybody enjoys to ignore. Following even the weakest level would be a starter, but not in current filesystems community. This needs to start in a new OS or with high profile spoofing attacks, such as on GitHub.