FileList overwritten by old one about csc HOT 2 CLOSED

Proposed solution: include version number with the file list. We would actually have two version numbers, one attached to the end of the filelist upload call and the other one embedded in the filelist data, signed by the public key. This is because peers not in the possession of the public key will still have to be able to determine which one of two filelists is the newer one. Malicious peers may report wrong numbers, even replay old messages with higher numbers, however when this filelist is read by someone else (assuming it is not the malicious peer that is responsible for storing the filelist), the reported version number will mismatch with the one embedded in the replayed data hence the operation will fail. This is consistent with our goal of allowing malicious peers to corrupt the data as long as we always can tell if the data is not authentic.

from csc.

solution implemented in commit c467877

from csc.