On 22/07/16 13:21, Chris Drake wrote:
Hi Yaron,
Best I can tell, everyone has jumped onto solving a cool problem,
without there actually being any reason to solve it?
I asked about the use case, and CDN authority revocation was all I got
(imho a really *weak* reason). Maybe I got it wrong?
What *exactly* is a use case for short-term certificates? What about
HSTS/HPKP?
Why would *any* expired short-term certificate be useful? Practically
no ordinary user cares about bad certs - heck - iPhone users don't even
have a way to check a cert even if they wanted to.
Kind Regards,
Chris Drake
Hi Chris,
Can you please explain why CDN authority revocation is a weak use case?
Let me share my preferred use case: I am running a large web property in
the cloud, where TLS connections are terminated on a cloud-based load
balancer (Amazon ELB, for a concrete example). I would like the cloud
provider to present my identity (www.example.com), but I want to revoke
this authority as soon as something bad happens, e.g. the cloud provider
is breached.
There may be alternative solutions, but I think short-term certs are a
reasonable solution here. Either the content owner gives the cloud
provider a new cert every X days (option 1), or the cloud provider can
get the short-term cert directly from the CA (option 2).
A solution that certainly CANNOT work is to give the cloud provider a
regular 1-year cert and revoke it if a breach occurs. Because we know
that cert revocation doesn't work.
Thanks,
Yaron
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme
