3 ms·
not sure but it seems the answer is trivial. a public api with checksum of all www files or a http header of the checksum, ie a new http method "CHKSUM /url/fi
by mc_hammer 12y ago
not sure but it seems the answer is trivial.
a public api with checksum of all www files or a http header of the checksum, ie a new http method "CHKSUM /url/file" possibley the nodes should not know if they are exit nodes, and then the checksum can be compared via 3-4 nodes.
if tor then compiled a list of nodes sending viruses the bad nodes could be cleaned out.
imo it would be nice if http had this for every page also; we could then have a browser plugin to verify checksums over https+3rd party to stop mitm attacks.
- GhotiFish 12y agoWhile I doubt the downvotes are necessary, you're misunderstanding the scope of a MITM attack. In order to mitigate a MITM you must in some way communicate with someone else. Your checksum idea either gets routed through the malicious node, which means they could change it, or it doesn't, which means you're revealing to some third party other than the exit node what it is you're browsing, and you're also telling them who you are. In a sense, this is what https is for, by trusting certificates you know to be valid, a malicious node won't be able to see, let alone manipulate the data being sent to you (Though obviously they will see who you're talking to.)