News for hackers. Stuff that matters.
Re:APFS is not safe to use with names which have Unicode nor... by rurban on Tuesday June 06, 2017 @11:57AM (#14498190)
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/ Combining marks or RTL switching tricks are the other popular spoofs.
Re:APFS is not safe to use with names which have Unicode nor... by cryptonector on Tuesday June 06, 2017 @05:21PM (#14501457)
Confusables 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.

Re:APFS is not safe to use with names which have Unicode nor... by Piskvorrr on Wednesday June 07, 2017 @04:56AM (#14504663)
1Il|!
Re:APFS is not safe to use with names which have Unicode nor... by kps on Tuesday June 06, 2017 @11:54PM (#14503626)

  > Any filename (directory entry as identifier) must forbid mixed scripts.
So I'm not allowed to name my files “A=πr²” or “10kΩ Резисторы”?
Re:APFS is not safe to use with names which have Unicode nor... by rurban on Wednesday June 07, 2017 @08:35AM (#14505776)
According 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.
Re:APFS is not safe to use with names which have Unicode nor... by kps on Wednesday June 07, 2017 @11:34AM (#14507255)
I 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.

Re:APFS is not safe to use with names which have Unicode nor... by rurban on Wednesday June 07, 2017 @05:45PM (#14510107)
The 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.