Mar 06 2020 28 mins 532
Cloudflare recently embarked on an epic quest to choose a CPU for its next-generation server build, so we explore the importance of requests per watt, the benefits of full memory encryption, and why AMD won.
Plus Mozilla's rollout of DNS over HTTPS has begun, a big milestone for Let's Encrypt, and more.
Links:
- Firefox continues push to bring DNS over HTTPS by default for US users - The Mozilla Blog
- The Facts: Mozilla’s DNS over HTTPs (DoH)
- Security/DOH-resolver-policy - MozillaWiki
- HTTPS for all: Let’s Encrypt reaches one billion certificates issued | Ars Technica
- Let’s Encrypt Has Issued a Billion Certificates - Let’s Encrypt - Free SSL/TLS Certificates
- Let’s Encrypt: A History - The Morning Paper
- Apple drops a bomb on long-life HTTPS certificates: Safari to snub new security certs valid for more than 13 months • The Register
- Ballot SC22: Reduce Certificate Lifetimes
- Google Chrome’s fear of Microsoft Edge is revealing its bad side
- Microsoft shares a roadmap for the new Microsoft Edge
- Microsoft Edge: Top Feedback Summary for March 4
- Download Microsoft Edge Insider Channels
- Flaw in billions of Wi-Fi devices left communications open to eavesdropping | Ars Technica
- kr00k: A serious vulnerability deep inside Wi-Fi encryption
- Kr00k Paper
- Technical Details of Why Cloudflare Chose AMD EPYC for Gen X Servers
- An EPYC trip to Rome: AMD is Cloudflare’s 10th-generation Edge server CPU
- Cloudflare’s Gen X: Servers for an Accelerated Future
- Impact of Cache Locality
- Gen X Performance Tuning
- Securing Memory at EPYC Scale
- Intel promises Full Memory Encryption in upcoming CPUs | Ars Technica
