jsSHA

It currently implements these SHA algorithms: SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512.

jsSHA is cross-browser tested and will allow developers to encrypt their strings with a greater security level.

What is new in this release:

• Fixed major issue with all hashes failing if raw input was a particular size.

What is new in version 2.0.1:

• Fixed major issue with all hashes failing if raw input was a particular size.

What is new in version 1.6.0:

• Added a BYTES input and output format that is a raw byte string
• Fixed broken AMD support (thanks drewcovi!)
• Fixed broken UTF-8 parsing on non-BMP Unicode characters
• Changed array references to remove warnings on Icedove
• Replaced "UTF16" encoding with "UTF16BE" (big endian) and "UTF16LE" (little endian) to remove confusion

What is new in version 1.5.1:

• Changed Google Closure Compiler options to produce "strict" compatible code.

What is new in version 1.5.0:

• Added optional numRounds argument to getHash
• Reduced file size by optimizing internal constants
• Removed charSize input and replaced with encoding to handle Unicode.
• Changed method of referencing "window" to be compatible with WebWorkers, Node.js, and AMD

What is new in version 1.42:

• Re-added v1.4 Safari patch to support older versions.

What is new in version 1.41:

• Fixed incorrect hash issue with Chrome x64 v25 (Dev channel), also provides stable patch to v1.4 Safari issue.

What is new in version 1.4:

• Added new input type, TEXT, that is functionally identical to ASCII*
• Added new input type, B64, for base-64 encoded strings
• Added new input and output formatting parameters

What is new in version 1.31:

• Updated project URL to point to new GitHub repository
• Added a compressed version of sha.js

What is new in version 1.2:

• Added the HMAC algorithm for all supported hashes (using both ASCII and hex keys)
• As a result of adding HMAC, added support for hash input text to be hex (ASCII representation of hex)
• Added multiple variants of safeAdd functions, resulting in a significant performance gain
• Removed wrapper.js file
• Used a different JavaScript compressor resulting in smaller file sizes

Requirements:

• JavaScript enabled on client side