LogoTurboSFV - Blog
 Home
Sign Posting and additional functions are only available, if you can be identified by using a session cookie. By clicking on Set Cookie, the server sends a cookie to your browser and instructs your browser to remove the cookie after 4 hours. Cookies must be enabled in your browser.
Icon TurboSFV
Icon 2026-07-18 12:03:51
TurboSFV v11.11 - Error fixed in SHA-1 SSE implementation
Notes to TurboSFV v11.11:

TurboSFV offers for SHA-1 a special SSE (Streaming SIMD Extensions) based implementation, in addition to the standard implementation. It allows to calculate checksums in a parallel manner and thus faster. In this implementation there was one assembler statement, which caused problems on some specific CPU types: The calculation didn't start at all or the application closed without a warning or error message.

Affected were basically all modules in the application, which can use the SSE implementation for SHA-1: If in the configuration in TurboSFV, on page "Calculation", the option "SHA-1 Use SSE instruction" was checked, then the main program didn't validate SHA-1 checksums and new checksum files with SHA-1 checksums couldn't be created. Also the shell property sheet page "Hash" didn't work, if SHA-1 was selected. The command-line versions didn't calculate checksums, if the switch "/d:1" in combination with SHA-1 was specified. Same problem with the service module, where for a job, the parameter "SSE" together with SHA-1 was specified.

Not affected: All other available hash algorithms and the standard implementation for SHA-1, which uses basic x86/x64 instructions. So, the workaround was to remove the check mark from "SHA-1 Use SSE instruction" in the configuration, not to use the SSE switch together with SHA-1 in the command-line versions and not to specify SSE for SHA-1 service jobs.

Again, the problem occurred only on specific CPU types, and thus was hard to detect. Many thanks to a customer with such a CPU, who flagged this issue and helped out with testing. The library with the faulty statement could be located and the statement could be adjusted, in order to work on all CPU types.

Feel free to add a comment regarding this new version here.
TurboSFV
Cologne, Germany




Back to list
 
 



Privacy Policy