6 ms·
How does this project prevent that I as an attacker insert random garbage or rewrite the downloaded pages to be wrong in specific ways? For HTTP this seems imp
by nh2 2y ago
How does this project prevent that I as an attacker insert random garbage or rewrite the downloaded pages to be wrong in specific ways?
For HTTP this seems impossible. For HTTPS, who does the TLS termination? It could be safe if the warrior was just at TCP proxy and Archive was the TLS client, but https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior doesn't seem to explain that clearly.
- kalleboo 2y ago> How does this project prevent that I as an attacker insert random garbage or rewrite the downloaded pages to be wrong in specific ways? It doesn't, but in practice, it's not a problem. The goal is to with minimum turnaround rescue as much data as possible before a site goes down. Getting 1% garbage is more preferable than losing 30% to inefficiency in archiving because you're paranoid. > For HTTPS, who does the TLS termination? The Warrior literally just runs wget and saves to warc files that are uploaded to a tracker server.