"The Security of Emojis"
summary
Tests show Windows Terminal renders emojis while conhost shows replacement boxes and Windows Terminal renders emojis. Hostnames and domain names accept emoji characters but NetBIOS names reject them, and Exchange rejects emoji FQDNs during verification. IIS serves emoji domains via punycode but SharePoint login fails; RDP accepts emoji-only logons that the local keyboard cannot type. Nmap prints emoji bytes, Metasploit mostly handles them, Wireshark shows placeholders, volatility survives, and ~3,500 emoji glyphs (Sep 2020) expand password entropy yet Windows policy treats them as non-compliant.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:14Emojis in Windows
- 2:55Emoji domain names
- 5:14Nonstandard emojis
- 8:17Password complexity
- 9:15Emoji password cracking
- 11:28Wireshark
- 15:11SharePoint
- 17:59macOS
- 19:47Questions
related talks
58mThe Power ⚡️ and Responsibility 😓 of Unicode Adoption ✨
49mThe Evolving Role of Emojis in Investigations and Data Security
59mBrowsers Gone Wild
41mWeaponizing Plain Text: ANSI Escape Sequences as a Forensic Nightmare
10mThe emoji that Killed Chrome!!
31mHow a Single ß Can Break Everything
40mHostSplit: Exploitable Antipatterns in Unicode Normalization
51mCharBusters - 10 Unicode Myths