Register the SHA1 fingerprint plugin for future use.
SHA1 can be used to calculate a checksum to verify that a 'message' has not been altered. Unlike CRC32 it is nearly impossible to modify the original message and still produce the same SHA1 fingerprint.
Here is a quick explanation taken from the RFC 3174 on SHA1:
'The SHA-1 is called secure because it is computationally infeasible to find a message which corresponds to a given message digest, or to find two different messages which produce the same message digest. Any change to a message in transit will, with very high probability, result in a different message digest, and the signature will fail to verify.'
More information can be found in the RFC 3174: http://www.ietf.org/rfc/rfc3174.txt.
UseSHA1Fingerprint() Debug StringFingerprint("yourpassword", #PB_Cipher_SHA1)
UseMD5Fingerprint()(), UseSHA2Fingerprint()(), UseSHA3Fingerprint()(), UseCRC32Fingerprint()()