MashupOS

Protection and communication abstractions for web browsers in MashupOS

• Where was it written - for OS people
  • Proceedings of twenty-first ACM SIGOPS symposium on Operating systems principles

Pages 1-16

• • Not security and not web people
• What the purposed
  • Written by the same people as subspace paper
    • Which came first ?
  • Sandbox EVERYTHING <-- solution to everything
• What the implemented
  • Sandbox
    • private that is hosted at and belongs to the integrator ??
  • Opensandbox
    • Ment for any scripted hosted on any domain
  • Service Instance
    • think starting a new process in linux - each alocated it's own resources
    • each service request
  • Commservice request - aka "Ports"
    • Allows separate components to talk to each other threw the parent , but never directly child to child
  • friv
    • the display driver each service instances needs it own display aka friv
  • vop <-- Do we want to talk about
  • sop <-- Do we want to talk about
• What was implemented
  • Proxy server and MME filter
• What the testing was
  • Running speed tests not security test , Anil said WHY ? mabey because OS conference cares about speed
  • Open sandbox was not implemented
  • only one service instance per friv
• Conclusions
  • Mostly a theoretical paper
    • But interesting
  • Notes
    • Do we want to show figure 2 <---- for what they did
    • Do we want to show figure 3 <--- for what they did and how it works