3 ms·
When you want a piece of information be authentic, chances are high that the information is also of private nature. It would be trivial to add something like <
by nine_k 12y ago
When you want a piece of information be authentic, chances are high that the information is also of private nature.
It would be trivial to add something like <rel signatory="https://this.same.domain/verify" https://this.same.domain/verify" algorithm="sha2"/> to any web page, or an HTTP header of the same nature, and run an HTTPS endpoint to check the url/signature pair. Probably international news agencies could run this, so that the proverbial China government would be able to see that a web page has nothing subversive on it, but anyone could see that the page has not been tampered with, by running a checksum against the page source. A browser extension could be used for that.
But it seems that nobody cares enough.
- untitaker_ 12y agoYou can MITM the unencrypted page and cut that HTML tag out.
- sanxiyn 12y agoYou can send (lightweight) HTML page and subresource hashes in secure channel, and deliver fonts and images and videos in cleartext without compromising on integrity.
- untitaker_ 12y agoOf course, I'm just arguing against the particular detailed proposal `nine_k` made.
- the_mitsuhiko 12y ago> When you want a piece of information be authentic, chances are high that the information is also of private nature. That's not true at all. For instance that we fetch web fonts via SSL is just because there is no other way to verify the identity of the webfont otherwise. There is nothing inherently private about a web font. The same applies to Python packages on PyPI etc.