News for hackers. Stuff that matters.
Re:Fight back against Google AMP (2018) by Ajedi32 on Wednesday December 04, 2019 @01:35PM (#21705351)
> one may manage to upload an html file to the bank's server and serve a -signed- page that google amp will cache

Only if you have the bank's private key, and the ability to serve arbitrary content from the bank's domain. In which case... yeah, I don't see how the signed exchanges standard makes that problem significantly worse.

Re:Fight back against Google AMP (2018) by buboard on Wednesday December 04, 2019 @01:46PM (#21705503)
i don't know what's the max expiration for amp's cache, but i could set a really-long expiration date on the file and remove it from the server without the bank ever knowing it existed. SGX don't even require an upload - one disgruntled employee could do the same with a stolen key.

Nobody benefits from this shit than google. Do we really need more attack surfaces?