úÎ`G      Safe-Infered"An abstract datatype for digests. ICompute the SHA-1 hash of the given ByteString. The output is guaranteed G to be exactly 160 bits, or 20 bytes, long. This is a good default for M programs that need a good, but not necessarily hyper-secure, hash function. HCompute the SHA-224 hash of the given ByteString. Note that SHA-224 and J SHA-384 differ only slightly from SHA-256 and SHA-512, and use truncated / versions of the resulting hashes. So using 224/384 may not, in fact, save  you very much ... KCompute the SHA-256 hash of the given ByteString. The output is guaranteed J to be exactly 256 bits, or 32 bytes, long. If your security requirements K are pretty serious, this is a good choice. For truly significant security = concerns, however, you might try one of the bigger options. GCompute the SHA-384 hash of the given ByteString. Yup, you guessed it, 9 the output will be exactly 384 bits, or 48 bytes, long. FFor those for whom only the biggest hashes will do, this computes the G SHA-512 hash of the given ByteString. The output will be 64 bytes, or  512 bits, long. Compute an HMAC using SHA-1. Compute an HMAC using SHA-224. Compute an HMAC using SHA-256. Compute an HMAC using SHA-384. Compute an HMAC using SHA-512. Convert a digest to a string. : The digest is rendered as fixed with hexadecimal number.  Convert a digest to an Integer. "Convert a digest to a ByteString.  secret key message  SHA-1 MAC  secret key message  SHA-224 MAC  secret key message  SHA-256 MAC  secret key message  SHA-384 MAC  secret key message  SHA-512 MAC           SHA-1.5.0.0Data.Digest.Pure.SHADigestsha1sha224sha256sha384sha512hmacSha1 hmacSha224 hmacSha256 hmacSha384 hmacSha512 showDigest integerDigestbytestringDigest$fBinarySHA512State$fBinarySHA256State$fBinarySHA1State$fBinaryDigest$fBinaryDigest0$fBinaryDigest1 $fShowDigest