Ray Nicholus

As far as I know, hash calculation time is proportional to the size of the file to be hashed. There is nothing we can do about this, as far as...

related to #848

@shehi Funny you mention this - I already had to implement file hashing client-side in order to support version 4 signature support in Fine Uploader S3 (see #1336 for details)....

Small chunk hashing is restricted to Fine Uploader S3, and only when generating version 4 signatures. I feel that this feature needs more input from other users before I consider...

> As I said, partial (as in few chunks) hashing should do the trick I'm not convinced that this is the correct approach, and am apprehensive about codifying this as...

The per-chunk checksum is already being calculated to support S3 v4 signatures, though it's not being used anywhere else at the moment. If each chunk is hashed, there isn't a...

> Is there currently a way to use the per chunk checksum when using a traditional server (not S3)? No, but it likely wouldn't be very difficult to integrate this...

This is something I'm looking into now. I don't see this being a feature implemented inside the Fine Uploader codebase. Instead, a couple small changes will be needed to make...

> Wouldn't this allow anyone to add a file to their own uploads as long as the hash is known of any file on the server I'm not sure I...

> another user could simply send 123 as a hash faking a upload with that hash and gain access to my foo.docx. How would they "gain access"? As I said...