Enterprise Linux crypto story
summary
Red Hat Enterprise Linux centralizes crypto into a small set of core crypto components so all apps use certified, reviewable code; validation includes regression testing, standards compliance tests and certification paths for FIPS, Common Criteria and PCI requirements. A custom TLS fuzzer tests RFC conformance and malformed inputs; crypto policies expose four profiles (modern, legacy, future, FIPS) to control algorithms and key sizes. Upstream contributions and CI, API/ABI stability, and country export/patent reviews determine which libraries are chosen.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:16Agenda
- 1:39Changes with time
- 5:52Quality
- 8:49Certification
- 9:03Crypto Components
- 10:49Quality Assurance
- 13:30Crypto Policies
- 16:53Project Stability
- 17:51Project Quality
- 19:50Summary
related talks
36mSecurity compliance: A global perspective
32mELC 2013 Security: Best Practices for Embedded Systems
13mIBM Secure Execution for RedHat CoreOS
35mKeeping the linux kernel secure across 10+ RHEL releases
14mThe Hidden Risks of Running AlmaLinux without Enterprise Support
29mAre Our Systems Using up-to-Date Cryptography?
28mAlmaLinux Security Feature Evaluation and Certifications — Efforts Toward FIPS 140-3 and CC Certification
26mIntegrity