Summary by TwinMind · 7m 52s
Summary by TwinMind · 7m 52s

A Christmas Computer Bug, and the Future of Files

A Christmas Computer Bug, and the Future of Files

Tom Scott

Tom Scott

Historical Context - December 1987

  • Ronald Reagan US President, Margaret Thatcher British PM
  • Home computers existed but not networked
  • World Wide Web still 2 years from invention
  • Computing era: text-based systems, state-of-the-art at time

CHRISTMA Computer Worm

  • Created by German university student
  • Name limited to 8 characters due to file naming constraints
  • Targeted one type of old text-based computer system
  • Functionality:
    • Displayed Christmas tree text art
    • Accessed computer's address book equivalent
    • Emailed itself to all contacts with message "Let this exec run and enjoy yourself"
  • Impact:
    • Took down IBM network for couple days (when IBM major force)
    • Resurfaced 3 years later when someone reopened forgotten file
    • Relatively innocent by modern ransomware/identity theft standards

Modern Malware Comparison

  • Similar attack vectors still possible on modern hardware
  • Current spread methods:
    • User downloads and runs malicious programs
    • Pirated software websites replace email as distribution vector
    • Zero-day attacks on Flash (frequent target)
    • Zero-day = no warning, immediate infection to patch cycle
  • Malware gains access to: internet, webcam, personal documents, everything

Current Security Mitigations

  • Windows: User Account Control, built-in antivirus
  • Mac/Linux: administrator accounts, permission management
  • Limitations:
    • Users often click OK or enter passwords inappropriately
    • Even without admin access, malware can:
      • Encrypt personal files (photos, business invoices)
      • Demand Bitcoin ransom payments
      • Computer cannot distinguish malicious vs legitimate user actions
  • Challenge: Creating malicious behavior filters requires near-perfect model of user intent

Alternative Security Architecture - Mobile Model

  • iPhone approach: each app has separate document storage area
  • No central accessible space for all apps
  • File sharing requires explicit app-to-app pushing
  • Desktop equivalent would mean:
    • Word documents only accessible within Word
    • Music only accessible in download player until pushed elsewhere
    • Email attachments require opening source app first

Technical Community Resistance

  • Advanced users object to restricted access
  • Need for program chaining and system customization
  • "Bodging" and advanced mode necessary for power users
  • Deep system access required for technical work

Historical Design Constraints

  • Desktop computers descended from 1987 systems
  • Original limitations:
    • Insufficient storage space for app silos
    • Limited processing power for separate management
    • Programs wrote direct binary data
    • Academic/professional use requiring careful equipment handling
  • Backwards compatibility prevents clean breaks
  • Apple provides few years grace period for updates
  • Windows runs programs from 20+ years ago
  • Never had option to start fresh

Modern Device Evolution

  • Tablets, phones, Chromebooks use locked-down systems
  • Behind scenes still use folders/files but hidden from end users
  • As these devices gain popularity, PC market share declining for home use
  • Potential to finally abandon old system architecture
  • Computer security could improve significantly

Educational and Development Concerns

  • Britain's tech industry strength from 1980s home computer boom
  • BBC Micro and ZX Spectrum created coding generation
  • Government push for computer literacy in children
  • Critical issue: "you can't write iPhone apps on an iPhone"
  • Someone must write the iPhone apps
  • Tension between security and development capability

Conclusion

  • Choice between traditional laptop (files/folders) vs modern phone (data silos)
  • Security vs accessibility tradeoff
  • Emphasis on creativity and making things (code, art, snowman)