7.The caching computer encrypts the blocks with an encryption key that is derived from the content metadata (using AES 128 by default) and sends it to the client.

8.The client decrypts the data by using the same encryption key that the caching computer. The client and the caching computer compute the same encryption key because they derive it from the same content metadata, which is sent by the content server.

9.After the client decrypts the data, it validates that the data is not corrupted or tampered. To do this, the client computes the block hashes on the blocks received, and then compares them to the block hashes received in the content metadata from the server. If the hashes do not match, the client discards the data.

Hope it helps!
Cheers,
Augusto

I have a little question, I was on Tech.Ed Berlin and heard allot about branch cache.
I’m thinking in the security point of view.
I couldn’t find anyone that could answer my question, so after reading your blog, you might be able to answer my question.
A client request a file from offlcation, it’s gets the current file id, then broadcasts it out on it local subnet, requesting other clients for a copy of the file. No one replyes, and it starts downloading the file to it’s own cache.
If I understand til right, then by sniffing the network subnet, I will know what file the client is requesting, and thereby it would be possible to request the file and get a copy, wont it? ofcause there is some security encryption and so on, but in theory?

During a recent discussion on Windows 7 there were some soli ……