rs_shake128

Crates.iors_shake128
lib.rsrs_shake128
version0.1.2
sourcesrc
created_at2023-05-30 11:31:34.437166
updated_at2023-06-12 16:47:35.802795
description`rs_shake128` is a Rust implementation of the SHAKE128 cryptographic hash algorithm, part of the larger `rs_shield` project. This package provides SHAKE128 hashing functionality in a standalone manner, ideal for when only SHAKE128 is required. Alternatively, for those seeking a comprehensive set of cryptographic functions, this same algorithm is included within the broader `rs_shield` library bundle. The focus of `rs_shake128` and the larger project is on performance, safety, and openness, with a commitment to ongoing maintenance and enhancement.
homepagehttps://docs.rs/rs_shield/latest/rs_shield/
repositoryhttps://github.com/Azgrom/RustyShield
max_upload_size
id877817
size36,001
Rafael Lúcio (Azgrom)

documentation

README

rs_shake128

rs_shake128 is a Rust crate implementing the SHAKE128 Extendable-Output Function (XOF). This permutation-based function is designed for compatibility with Rust's libcore in a #![no_std] context, allowing it to operate as a standalone crate for specialized use cases and also function within a #![no_std], #![no_alloc] environment, rendering it suitable for systems where dynamic memory allocation is not feasible.

This implementation of SHAKE128 is compliant with the Federal Information Processing Standards (FIPS) Publication 2021. As per the National Institute of Standards and Technology (NIST) guidelines, SHAKE128 is recommended for various use cases:

"SHAKE128 and SHAKE256 are extendable-output functions (XOFs), which can output a hash of variable length, are approved for all applications using hash functions that can benefit from variable-length output."

Given this advice, NIST recommendations imply that SHAKE128 is suitable for the following contexts:

  • Digital signatures that require variable bits of security.
  • Cryptographic hash functions in systems and protocols requiring variable bits of security.
  • Authentication methods that necessitate variable bits of security.
  • Applications where the output length is not fixed.

Beyond these specific recommendations, SHAKE128 could also find application in:

  • Generation of unique identifiers in distributed systems2.
  • Data integrity checks in Merkle Trees3.
  • Hash-based message authentication codes (HMACs), when collision resistance is necessary4.
  • Key derivation functions or in generation of random numbers5.

These points should be carefully considered, given your overall security objectives and risk tolerance.

For access to a comprehensive range of cryptographic functions, rs_shake128 can be utilized as part of the rs_shield library bundle.

How To Use

Below are steps to use the rs_shake128 crate in your Rust projects:

  1. Add the following line to your Cargo.toml under the [dependencies] section:

    rs_shake128 = "0.1.*"
    
  2. Use the functions provided by the rs_shake128 module in your code. Here's an example of how to create a SHAKE128 hash from a string:

    use rs_shake128::{HasherContext, Shake128Hasher};
    
    let mut sha512_256hasher = Shake128Hasher::<20>::default();
    sha512_256hasher.write(b"your string here");
    
    let u64result = sha512_256hasher.finish();
    let bytes_result = HasherContext::finish(&mut sha512_256hasher);
    assert_eq!(u64result, 0x9105E04821D530DE);
    assert_eq!(format!("{bytes_result:02x}"), "9105e04821d530de80ff68fac42a0fe164c744dd");
    assert_eq!(format!("{bytes_result:02X}"), "9105E04821D530DE80FF68FAC42A0FE164C744DD");
    assert_eq!(
        bytes_result,
        [
            0x91, 0x05, 0xE0, 0x48, 0x21, 0xD5, 0x30, 0xDE, 0x80, 0xFF, 0x68, 0xFA, 0xC4, 0x2A, 0x0F, 0xE1, 0x64, 0xC7,
            0x44, 0xDD
        ]
    )
    

More Information

For a more detailed exploration of rs_shake128, an overview of other available cryptographic functions, and an introduction to the broader rs_shield project, please consult the RustyShield project page on crates.io.

Contributions

Potential contributors are encouraged to consult the contribution guidelines on our GitHub page.

License

This project is licensed under GPL-2.0-only.

References


Note: The references have been provided as per the best knowledge as of May 17, 2023.

Footnotes

  1. National Institute of Standards and Technology. (2015). SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions. FIPS PUB 202

  2. Linus Torvalds. (2005). Git: A distributed version control system. Software: Practice and Experience, 41(1), 79-88. DOI:10.1002/spe.1006

  3. Merkle, R. C. (1988). A Digital Signature Based on a Conventional Encryption Function. Link

  4. Krawczyk, H., Bellare, M., & Canetti, R. (1997). HMAC: Keyed-Hashing for Message Authentication. RFC 2104

  5. National Institute of Standards and Technology. (2012). Recommendation for Key Derivation through Extraction-then-Expansion. SP 800-56C

Commit count: 289

cargo fmt