4 ms·
If I understand correctly the digest is only to make sure it didn't change while in transit. If the file itself that's being served was compromised, the web se
by TimTheTinker 6y ago
If I understand correctly the digest is only to make sure it didn't change while in transit.
If the file itself that's being served was compromised, the web server will serve it with a new digest that matches.
- giantrobot 6y agoThat's where the Signature header comes in. The host can sign the resource and the client can verify the digest and signature. If you're trusting the TLS connection you'd have the same amount of trust in the resource signature.