5 ms·
Makes you wonder why unicode has invisible characters in the first place and why a compiler would interpret them at all.
by moffkalast 1y ago
Makes you wonder why unicode has invisible characters in the first place and why a compiler would interpret them at all.
- AnimalMuppet 1y agoThe compiler doesn't. They get passed to decode, and then to eval.
- h4ck_th3_pl4n3t 1y agoIt's not the compiler. It's JavaScript and its fucked up UTF-16 strings. UTF-16 should have been UTF-8 for a variety of reasons, and I thought we have learned from the Effective power لُلُصّبُلُلصّبُررً ॣ ॣh ॣ ॣ 冗 incident.
- amingilani 1y agoThe what incident? Can you elaborate? Edit: Here’s the incident-https://www.theregister.com/2015/05/27/text_message_unicode_ios_osx_vulnerability/ https://www.theregister.com/2015/05/27/text_message_unicode_...
- h4ck_th3_pl4n3t 1y agoNot only iOS was affected. MacOS, too. Firefox, too. Chromium, too. Essentially everything that used libicu as a unicode parser. Was quite fun posting this in IRC and other chats and seeing clients go offline at the time :)