Good Morning Guys, I'm currently looking into the Project Maelstorm (BitTorrent Peer-To-Peer Web Browser Project), and a question popped up in mind.
When on a P2P network, users share the file which originated from a single source, once the first user has downloaded the source, a hash check can be used to assure the file being transmitted by that user is not a modified one (With more users, this also blocks MITM attacks, because you can compare a big amount of hashes and see if they match before trusting anyone).
Now comes my question(s):
1: What about server-side scripts? For instance, let's say I have a website with a login page, how would my login-password info be checked? If that required a main server, we are no longer on a peer-to-peer web, if the database files were also transferred with the main website structure, wouldn't that be:
- A: Insecure? Passwords can be hashed, but what about personal information? (Which is needed on the website, for instance, your address on facebook?).
- B: Slow? Since a database can get constant updates (Let's think about 1.5k users updating their profiles constantly), that would need constant file hash re-check, consuming a lot of data on both ends.
2: DDoSes and Takedowns would be sent against what? The essence of P2P is to block both of these, if there was still a server-client way for data transferring, wouldn't that be easy for somone to DDOS the database server? And for govnt/isps to send takedown notices to database server hosts?
Thank you and have a good day. - Fabricio20