Hacker News new | ask | show | jobs
by stop_nazi 243 days ago
The problem with the horrible injections on the page can be solved very simply. If the information on a page is open, just pass that page openly and pass a checksum of page in the header. To prevent this sum from being tampered with, the server will encrypt it. Not the whole page, just the sum. You will save a lot of CPU time on server and on client, reduce CO₂ and so on
2 comments

So TLS with some "eNULL" ciphersuite. People have been there, tried that. There's very very little practical value in that over just doing proper encryption as well.
You aren't really saving anything. Hashing and encryption are very similar, so hashing the entire page is comparable to just encrypting it.