• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Verifying Software?

I understand that with typical single files a hash such as MD5, SHA1 or SHA256 is used for verification. However what's a good way if you have a large list of files? Say like 50 or 100 files or even more?

Part of the reason I ask is I was at work reading through some of our SOPs for releasing software--and by release I mean put software into our document control. This isn't necessarily meaning that we write the software ourselves, but any software like if we hire a contractor to develop a custom test software. Note we are NOT a software company, so pardon the inexperience. One of the procedures said to provide a file index snapshot (simple dir /s command) when . All you get is a list of files and file sizes, but how good of a process is this even? I dug further and found that we verify media that we receive for production (i.e. DVDs or flash disks) using this process too.

I'm not a software guy myself, but this seems to be a very low tech and risky way of verifying software was provided properly. By verifying a file index you're just comparing file sizes. Shouldn't we be checking hashes or something?
 
Back
Top