:: a typeCtrl KGHC 9.10.3 · lts/ghc-9.10.x · c74966e · 2026-09-27
ModuleSHA-1.6.4.4Haskell98
Pure implementations of the SHA suite of hash functions. The implementation is basically an unoptimized translation of FIPS 180-2 into Haskell. If you're looking for performance, you probably won't find it here.
An abstract datatype for digests.
Eq (Digest t)Defined in SHA-1.6.4.4 · Data.Digest.Pure.SHAOrd (Digest t)Defined in SHA-1.6.4.4 · Data.Digest.Pure.SHAShow (Digest t)Defined in SHA-1.6.4.4 · Data.Digest.Pure.SHABinary (Digest SHA1State)Defined in SHA-1.6.4.4 · Data.Digest.Pure.SHABinary (Digest SHA256State)Defined in SHA-1.6.4.4 · Data.Digest.Pure.SHABinary (Digest SHA512State)Defined in SHA-1.6.4.4 · Data.Digest.Pure.SHABinary SHA256StateDefined in SHA-1.6.4.4 · Data.Digest.Pure.SHABinary (Digest SHA256State)Defined in SHA-1.6.4.4 · Data.Digest.Pure.SHABinary SHA512StateDefined in SHA-1.6.4.4 · Data.Digest.Pure.SHABinary (Digest SHA512State)Defined in SHA-1.6.4.4 · Data.Digest.Pure.SHAConvert 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.
Compute the SHA-1 hash of the given ByteString. The output is guaranteed to be exactly 160 bits, or 20 bytes, long. This is a good default for programs that need a good, but not necessarily hyper-secure, hash function.
Compute the SHA-224 hash of the given ByteString. Note that SHA-224 and 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 ...
Compute the SHA-256 hash of the given ByteString. The output is guaranteed to be exactly 256 bits, or 32 bytes, long. If your security requirements are pretty serious, this is a good choice. For truly significant security concerns, however, you might try one of the bigger options.
Compute the SHA-384 hash of the given ByteString. Yup, you guessed it, the output will be exactly 384 bits, or 48 bytes, long.
For those for whom only the biggest hashes will do, this computes the SHA-512 hash of the given ByteString. The output will be 64 bytes, or 512 bits, long.
Similar to sha1 but use an incremental interface. When the decoder has been completely fed, completeSha1Incremental must be used so it can finish successfully.
Similar to sha224 but use an incremental interface. When the decoder has been completely fed, completeSha224Incremental must be used so it can finish successfully.
Similar to sha256 but use an incremental interface. When the decoder has been completely fed, completeSha256Incremental must be used so it can finish successfully.
Similar to sha384 but use an incremental interface. When the decoder has been completely fed, completeSha384Incremental must be used so it can finish successfully.
Similar to sha512 but use an incremental interface. When the decoder has been completely fed, completeSha512Incremental must be used so it can finish successfully.
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.