exploit Dropbox file redundancy check
in Dropbox if a file is already present at their servers, the file is not uploaded. It syncs instantly..

Now, this check is done on a few things i think, probably the file size, file name, and of course the CRC (md5 hash or something...)

I was thinking.. if I know the file name, its size and its CRC, is it possible to create a fake file that produces that particular CRC (reverse hashing) so that dropbox actually syncs the true file?

It's just an experiment, it could be done for example with linux distribution images..
any idea on the topic?
exploit Dropbox file redundancy check
===

in Dropbox if a file is already present at their servers, the file is not uploaded. It syncs instantly..

Now, this check is done on a few things i think, probably the file size, file name, and of course the CRC (md5 hash or something...)

I was thinking.. if I know the file name, its size and its CRC, is it possible to create a fake file that produces that particular CRC (reverse hashing) so that dropbox actually syncs the true file?

It's just an experiment, it could be done for example with linux distribution images..
any idea on the topic?