4 ms·
HTTPS is basically HTTP over TLS, so start with RFCs: - TLS v1.2 (https://tools.ietf.org/html/rfc5246 https://tools.ietf.org/html/rfc5246) - Certificate valid
by kbart 10y ago
HTTPS is basically HTTP over TLS, so start with RFCs:
- TLS v1.2 (https://tools.ietf.org/html/rfc5246 https://tools.ietf.org/html/rfc5246)
- Certificate validation (https://tools.ietf.org/html/rfc6960 https://tools.ietf.org/html/rfc6960)
- PKI is a little more tricky, as there's no single standard that defines it, though to get basic idea of what are certificates read RFC 5280 (https://tools.ietf.org/html/rfc5280 https://tools.ietf.org/html/rfc5280).
Sure, you can dig as deep as you want, but these resources should give you a good starting point.
- rkeene2 10y agoDon't forget RFC 2818 (HTTPS) which Chromium (and thus Chrome) recently broke mandatory features of: https://bugs.chromium.org/p/chromium/issues/detail?id=308330#c39 https://bugs.chromium.org/p/chromium/issues/detail?id=308330...
- NetStrikeForce 10y agoIs this a remake of that "embrace, extend, ..." movie of the 90s or this time it's cool?
- rkeene2 10y agoIt's really very similar. This is a case where the Chromium developers want to do something so they are going to do it, standards be dammed...