Why are file hashes not used for software activation?

The correct choice reflects the primary purpose of file hashes, which is to validate the integrity of files rather than to serve as a mechanism for software activation. File hashes are generated based on the contents of a file. When distributing software, the file hash can be used to ensure that the file has not been altered or corrupted since its creation. Thus, the primary use case for file hashes is in the realm of integrity validation.

In the context of software activation, relying solely on file hashes would not be effective because they do not inherently provide a unique identifier or a method for confirming that a user is authorized to use the software. Software activation typically requires more complex mechanisms that can include user credentials, license keys, or digital signatures, which are designed to verify the user's right to access the software rather than just confirm that a file has not been tampered with.

While file hashes are indeed public information, which is mentioned in another choice, this characteristic doesn't preclude their use for integrity checks. Similarly, the fact that file hashes do not change frequently can be a concern for dynamic applications but does not directly relate to the functionality required for software activation. Their inability to verify integrity is also inaccurate, as this is a primary function of hashes. Thus, the role of