Rust

AES GCM Encrypt and Decrypt a File

See more Encryption Examples

Demonstrates how to AES GCM encrypt and decrypt a file. Rust

// This example assumes the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.

let crypt = chilkat::Crypt2::new();

// Set the encryption algorithm to "AES"	
crypt.set_crypt_algorithm("aes");

// Indicate that the Galois/Counter Mode (GCM) should be used:
crypt.set_cipher_mode("gcm");

// KeyLength may be 128, 192, 256
crypt.set_key_length(256);

// This is the 256-bit AES secret key (in hex format)
let k = "000102030405060708090A0B0C0D0E0F000102030405060708090A0B0C0D0E0F".to_string();

// This is the 16-byte initialization vector (in hex format)
let iv = "000102030405060708090A0B0C0D0E0F".to_string();

// This is the OPTIONAL additional data (in hex format) to be used as input to the GCM AEAD algorithm,
// but is not included in the output.  It plays a role in the computation of the
// resulting authenticated tag.
let aad = "feedfacedeadbeeffeedfacedeadbeefabaddad2".to_string();

// Set the secret key and IV
crypt.set_encoded_iv(&iv, "hex");
crypt.set_encoded_key(&k, "hex");

// Set the additional authenticated data (AAD)
let _ = crypt.set_encoded_aad(&aad, "hex").is_ok();

// Encrypt a file.
let mut in_file = "qa_data/hamlet.xml".to_string();
let mut out_file = "c:/temp/qa_output/hamlet_aes_gcm.enc".to_string();
if crypt.ck_encrypt_file(&in_file, &out_file).is_err() {
    println!("{}", crypt.last_error_text());
    return;
}

// Get the authentication tag in hex format
let auth_tag = crypt.get_encoded_auth_tag("hex").unwrap_or_default();
println!("authentication tag = {}", auth_tag);

// Decrypt..

// Before decrypting, you must provide the expected authentication tag.
// The decrypt will fail if the resulting authentication tag computed while decrypting is not equal to the
// expected authentication tag.
let _ = crypt.set_encoded_auth_tag(&auth_tag, "hex");

in_file = out_file.clone();
out_file = "c:/temp/qa_output/hamlet_restored.xml".to_string();
if crypt.ck_decrypt_file(&in_file, &out_file).is_err() {
    println!("{}", crypt.last_error_text());
    return;
}

println!("Success.");

// --------------------------------------------------------------------------------------------
// About AES-GCM:

// AES-GCM (Advanced Encryption Standard - Galois/Counter Mode) is a widely-used
// encryption mode that provides both confidentiality (encryption) and
// integrity/authentication (data integrity verification) in one operation. It is
// commonly used in secure communications due to its efficiency and strong security
// properties.
// 
// Key Concepts:
// 
//     AES (Advanced Encryption Standard):
// 
//         AES is a symmetric encryption algorithm, meaning the same key is used
//         for both encryption and decryption.
// 
//         It operates on fixed-size blocks of data (128 bits) using key sizes of
//         128, 192, or 256 bits.
// 
//         In AES-GCM, AES is used to perform the actual data encryption.
// 
//     GCM (Galois/Counter Mode):
// 
//         Counter Mode (CTR): GCM uses counter mode for encryption. In this mode,
//         a nonce (or initialization vector, IV) and a counter are combined and encrypted
//         with AES. The result is XORed with the plaintext to produce the ciphertext. 
// 
//         Galois Mode (GMAC): GCM also includes an authentication mechanism based
//         on a Galois field. It generates an authentication tag, which ensures the
//         integrity of both the ciphertext and any additional data (called AAD -
//         Additional Authenticated Data). This tag is verified during decryption to ensure
//         that the data hasn't been tampered with.
// 
// Key Features:
// 
//     Confidentiality (Encryption):
// 
//         The plaintext is encrypted using AES in counter mode. Each block of
//         plaintext is XORed with the output of AES applied to a combination of the IV and
//         an incremented counter.
// 
//     Integrity (Authentication):
// 
//         In addition to encryption, GCM provides authentication for both the
//         encrypted data (ciphertext) and any Additional Authenticated Data (AAD), such as
//         headers or metadata that need to be protected but not encrypted.
// 
//         The authentication tag is generated using a Galois field multiplication
//         of the ciphertext and AAD. This ensures that any changes to the encrypted
//         message or the AAD will be detected during decryption.
// 
// Key Components:
// 
//     - Plaintext: The data you want to encrypt.
//     - Ciphertext: The encrypted data.
//     - Key: A symmetric key used for both encryption and decryption.
//     - Nonce/IV: A unique value used for each encryption to ensure security. It is not secret but should never be reused with the same key.
//     - AAD (Additional Authenticated Data): Optional data that is not encrypted but needs to be authenticated (e.g., headers).
//     - Authentication Tag: A tag generated to verify the integrity and authenticity of the ciphertext and AAD.