The Secure Socket API: TLS as an Operating System Service
summary
Argues that TLS belongs at the socket layer and demonstrates a prototype Secure Socket API implemented as a small kernel module that offloads crypto and validation to user‑space daemons, preserving POSIX call signatures. Shows concrete wins: 317 to 16 lines of code for a secure download, 504 symbols reduced to 14 exposed calls, no measurable throughput penalty versus OpenSSL, and successful ports of wget and lighty with <20 replacement lines; certificate validation is on by default and administrators can enforce global TLS policies.
AI-written summary · about
chapters (13)
- 0:00The state of TLS security
- 3:02Complexity of TLS integration
- 3:45Introducing the Secure Socket API
- 6:34Architecture of the SSA
- 7:40Measuring API efficiency
- 8:03Improving developer experience
- 8:29API design and reconnaissance
- 9:22Administrator-driven security
- 12:16Advanced certificate management
- 13:19Evaluation of SSA utility
- 14:44Multi-language support
- 16:10Performance and compatibility
- 18:01Discussion and Q&A
related talks
39mLeveraging the Linux Kernel for Building a Zero-Trust Environment With...
28mTrustBase: An Architecture to Repair and Strengthen...
44mSSL/TLS for Mortals
01h 01mHTTPS & TLS in 2016: Security practices from the front lines
40mGetting Started with the TPM2 Software Stack (TSS2)
58mSecure Networking with SSL
53mHansel and Gretel do TLS
37mOpenSSL Hardware Offload Enhancement