#cryptography #tink #aead

tink-aead

AEAD functionality for Rust port of Google’s Tink cryptography library

7 releases

0.2.4 Mar 25, 2022
0.2.3 Jan 3, 2022
0.2.1 Oct 8, 2021
0.2.0 May 24, 2021
0.1.0 Jan 21, 2021

#688 in Cryptography

Download history 500/week @ 2022-06-13 285/week @ 2022-06-20 248/week @ 2022-06-27 259/week @ 2022-07-04 158/week @ 2022-07-11 336/week @ 2022-07-18 312/week @ 2022-07-25 568/week @ 2022-08-01 265/week @ 2022-08-08 276/week @ 2022-08-15 136/week @ 2022-08-22 115/week @ 2022-08-29 178/week @ 2022-09-05 237/week @ 2022-09-12 193/week @ 2022-09-19 420/week @ 2022-09-26

1,028 downloads per month
Used in 3 crates

Apache-2.0

310KB
5K SLoC

Tink-Rust: Authenticated Encryption with Additional Data

Docs MSRV

This crate provides authenticated encryption with additional data (AEAD) functionality, as described in the upstream Tink documentation.

Usage

fn main() -> Result<(), Box<dyn Error>> {
    tink_aead::init();
    let kh = tink_core::keyset::Handle::new(&tink_aead::aes256_gcm_key_template())?;
    let a = tink_aead::new(&kh)?;

    let pt = b"this data needs to be encrypted";
    let aad = b"this data needs to be authenticated, but not encrypted";
    let ct = a.encrypt(pt, aad)?;
    println!("'{}' => {}", String::from_utf8_lossy(pt), hex::encode(&ct));

    let pt2 = a.decrypt(&ct, aad)?;
    assert_eq!(&pt[..], pt2);
    Ok(())
}

License

Apache License, Version 2.0

Known Issues

  • Before version 0.2.4, AES-CTR-HMAC-AEAD keys and the subtle::EncryptThenAuthenticate implementation may be vulnerable to chosen-ciphertext attacks. An attacker can generate ciphertexts that bypass the HMAC verification if and only if all of the following conditions are true:
    • Tink is used on systems where usize is a 32-bit integer. This is usually the case on 32-bit machines.
    • The attacker can specify long (>= 2^29 bytes ~ 536MB) associated data

Disclaimer

This is not an officially supported Google product.

Dependencies

~5MB
~68K SLoC