Concurrency Abstractions for Application Security
summary
Claims that Erlang/BEAM-style concurrency—isolated lightweight processes, message passing, and supervision trees implemented via OTP—shifts responsibility from app code to runtime, improving integrity, confidentiality and availability (cites GitHub cookie leak and TLS/Heartbleed as failure modes this model can limit), while trading raw throughput for simpler GC and crash-and-restart resilience. Compares real implementations: Elixir/Gleam on BEAM, Go goroutines/channels, Akka on JVM, Rust/Tokio, and points out missing security primitives like per-process access controls, code signing and complete static typing.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:51Agenda
- 2:52Flashback: Memory management
- 6:01Concurrency
- 9:05Concurrency abstractions
- 14:20Security potential
- 32:00Implementations
- 39:16Challenges & future work
- 42:10Outro
related talks
43mConcurrency Oriented Programming in a Modern World
40mComparison and Commentary on "Application Operating System"
42mConcurrency Oriented Software
39mConcurrent Languages are Functional
51mThe Erlang VM or How I Started Loving Parallel Progamming
49mBEAM Concurrency in Action
34mComparing the Actor model & CSP concurrency with Elixir & Clojure
39mLet's talk concurrency