🔥 Discover this trending post from Hacker News 📖
📂 **Category**:
✅ **What You’ll Learn**:
OpenSSL can’t validate the cert because it contains a critical extension it doesn’t recognize — specifically 1.2.840.113635.100.6.27.3.2, which is an Apple-proprietary OID marked as critical. Per X.509 rules, if a client encounters an unrecognized critical extension, it must reject the cert.
That said, this is likely intentional on Apple’s part — browsers and Apple’s own TLS stack (SecureTransport/Network.framework) almost certainly know how to handle this extension. It’s a private Apple CA (Apple Server Authentication CA) signing an Apple-internal service endpoint, so it’s designed to work within Apple’s ecosystem rather than with generic OpenSSL.
In practice:
- Works fine in Apple clients (Safari, curl on macOS using the system TLS stack, iOS apps)
- Fails with raw OpenSSL or other non-Apple TLS implementations
- Not a misconfiguration — it's Apple intentionally using a proprietary critical extension on their private PKI
💬 **What’s your take?**
Share your thoughts in the comments below!
#️⃣ **#Apple #development #certificate #server**
🕒 **Posted on**: 1773190392
🌟 **Want more?** Click here for more info! 🌟
