On Wed, Dec 06, 2023 at 01:27:02PM +0000, Peter Gutmann wrote: > Filippo Valsorda <[email protected]> writes: > >I am not sure what you mean by key continuity being adopted for PKI use > > I meant the use of certificate pinning, so trusting the known-good cert you've > seen before and, like SSH when a key changes, triggering an alert if it > changes.
Trusting a *cert* you've seen before and popping up a warning when it changes seems like an absolutely terribad idea, given certs are designed to expire. Trusting the *key* underlying the cert, and having the user perform an action when the key changes, is arguably better (at least keys don't *have* to change, by Root Store policy, on a regular basis) but the closest thing to that I can think of to that is HPKP[1], but that's not a TOFU key scheme, but is instead the site declaring which key(s) are valid for itself. When has "true" cert/key TOFU been deployed in a WebPKI context? - Matt [1] which Chrome nuked some years ago, IE, Edge, and Safari never implemented, and which is default-off in Firefox, according to https://en.wikipedia.org/wiki/HTTP_Public_Key_Pinning -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/2f4f56f2-6ef7-464c-a900-6a6a7b7d1b60%40mtasv.net.
