News for hackers. Stuff that matters.
Re:HTTP Immutable Responses by prolurker on Friday September 15, 2017 @07:49PM (#15261798)
That's an interesting attack vector, in the section 3 of the RFC they recommend to ignore the directive unless it's a secure connection which would mitigate that kind of problems.

Another solution would be to use an unpredictable versioning scheme so the attacker can't anticipate the name of the resources.

Re:HTTP Immutable Responses by AgentME on Friday September 15, 2017 @08:01PM (#15261849)
The attacker who buys a bunch of domains and legitimately owns them for a period of time wouldn't have any issue getting SSL certificates for them.
Re:HTTP Immutable Responses by prolurker on Friday September 15, 2017 @08:11PM (#15261908)
Correct, but, even if not explicitly said, the cached entries should be associated to the certificate's fingerprint and immediately discarded once the certificate expires or is changed.
Re:HTTP Immutable Responses by rav on Saturday September 16, 2017 @03:33AM (#15263430)
Certificates often change for legitimate reasons, e.g. Let's Encrypt certificates which must be changed every 3 months.
Re:HTTP Immutable Responses by geon on Saturday September 16, 2017 @04:30AM (#15263601)
That would be ok.