When files are split, add an option to checksum the original (whole) file. This allows us to verify integrity when the files are joined into the original.
Store the checksum as a BFS file attribute in every split file. However, if a self-extracting executable is generated we can store the checksum only in the executable.
Checksums will slightly increase the size of each split file but since this is optional, the user can decide if file size is more important than being able to verify integrity (or he can of course, do it manually himself, hence optional).
The idea is to pick the checksum algorithm with speed in mind rather than collision resistance but at least as good as MD5 or something better (and faster).
When files are split, add an option to checksum the original (whole) file. This allows us to verify integrity when the files are joined into the original.
Store the checksum as a BFS file attribute in every split file. However, if a self-extracting executable is generated we can store the checksum only in the executable.
Checksums will slightly increase the size of each split file but since this is optional, the user can decide if file size is more important than being able to verify integrity (or he can of course, do it manually himself, hence optional).
The idea is to pick the checksum algorithm with speed in mind rather than collision resistance but at least as good as MD5 or something better (and faster).