…aintaining and securing the federation metadata, which includes public key pins RFC7469 , issuer certificates, and other essential information. Additionally, the federation operator SHOULD develop their own threat models to proactively identify potential risks and threats. This p…
…intaining and securing the federation metadata, which includes public key pins [RFC7469], issuer certificates, and other essential information. Additionally, the federation operator SHOULD develop their own threat models to proactively identify potential risks and threats. This p…
…matching a set of SPKI Fingerprints in an analogous manner to that described in RFC7469 ]. With this out-of-band key-pinned privacy profile, client administrators SHOULD deploy a backup pin along with the primary pin, for the reasons explained in [ RFC7469 ]. A backup pin is espe…
…TTP Strict Transport Security (HSTS) RFC6797 and HTTP Public Key Pinning (HPKP) RFC7469 . HSTS allows websites to declare themselves accessible only via secure connections, and HPKP allows websites to declare their cryptographic identifies. Similarly, Expect-CT allows websites to…
…TTP Strict Transport Security (HSTS) RFC6797 and HTTP Public Key Pinning (HPKP) RFC7469 . HSTS allows websites to declare themselves accessible only via secure connections, and HPKP allows websites to declare their cryptographic identifies. Similarly, Expect-CT allows websites to…
… means something subtly different than HTTP Public Key Pinning as described in [RFC7469]. The dual use of the same term is confusing, but unfortunately both uses are well established.) Moore & Newman Standards Track [Page 15] RFC 8314 Use of TLS for Email Submission/Access Januar…
…means something subtly different than HTTP Public Key Pinning as described in [ RFC7469 ]. The dual use of the same term is confusing, but unfortunately both uses are well established.) Moore & Newman Standards Track [Page 15] RFC 8314 Use of TLS for Email Submission/Access Janua…
…ary. Implementations MUST perform any certificate-pinning validation (such as [ RFC7469 ]) on alternative services just as they would on direct connections to the origin. Implementations might also choose to add other requirements around which certificates are acceptable for alte…
…ers providing hex encoding of the peer’s public key, while ’pin-sha256:’ is the RFC7469 key PIN, which utilizes base64 encoding. To ease certain testing use-cases, a partial match of the hash will also be accepted, if it is at least 4 characters past the prefix. --useragent=STRIN…