Securing Elixir Applications
summary
EPMD and the BEAM bind to all interfaces by default so bind EPMD to loopback (env var or start epmd -address) to avoid exposing the remote shell; swap in the TLS distribution module for mutual TLS/PSK and confidentiality; get an A+ on SSL Labs by supplying custom Diffie‑Hellman params, ordering ciphers (six modern suites) and adding HSTS via the plug; HTTPc trusts everything until given a CA bundle so use the Mozilla trust store and verify hostname; atoms aren’t GCed — converting external strings to atoms can crash the VM; strip beams with mix no_debug_info.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:57Erlang node security
- 13:57TLS and SSL configuration
- 24:03Secure client implementation
- 31:53System robustness and threats
- 40:03Bonus: TLS test server
related talks
37mSecurity of the BEAM
25mFIPS 140-2 in BEAM Apps
41mFireside chat on security for practitioners & academics
41mEnd to End Encryption with Elixir and Beam
32mDon’t let it crash: How we applied our security checks on Elixir code
18mSecuring Erlang and Elixir applications
40mLearn you some 'ssl' for much security!
46mEnarx - Attested, Secured Execution with AMD’s SEV