EVP_CIPHER-AES(7ossl)

📦 version 3.5.0, in opensuse-leap 16.0

💅 NAME 💅

EVP_CIPHER-AES — okay so this is the OpenSSL manual page for EVP_CIPHER-AES, section 7ossl — slay, it's literally all about the AES EVP_CIPHER implementations. Bestie, it's giving support for AES symmetric encryption using the EVP_CIPHER API. Periodt. 💖

🦋 DESCRIPTION 🦋

The whole vibe is support for AES symmetric encryption using the EVP_CIPHER API. No cap. This is the main character energy of the page, fr fr. ✨

🌸 Algorithm Names 🌸

Okay so vibe check: the following algorithms are available in the FIPS provider as well as the default provider:

  • "AES-128-CBC", "AES-192-CBC" and "AES-256-CBC"
  • "AES-128-CBC-CTS", "AES-192-CBC-CTS" and "AES-256-CBC-CTS"
  • "AES-128-CFB", "AES-192-CFB", "AES-256-CFB", "AES-128-CFB1", "AES-192-CFB1", "AES-256-CFB1", "AES-128-CFB8", "AES-192-CFB8" and "AES-256-CFB8"
  • "AES-128-CTR", "AES-192-CTR" and "AES-256-CTR"
  • "AES-128-ECB", "AES-192-ECB" and "AES-256-ECB"
  • "AES-192-OFB", "AES-128-OFB" and "AES-256-OFB"
  • "AES-128-XTS" and "AES-256-XTS"
  • "AES-128-CCM", "AES-192-CCM" and "AES-256-CCM"
  • "AES-128-GCM", "AES-192-GCM" and "AES-256-GCM"
  • "AES-128-WRAP", "AES-192-WRAP", "AES-256-WRAP", "AES-128-WRAP-PAD", "AES-192-WRAP-PAD", "AES-256-WRAP-PAD", "AES-128-WRAP-INV", "AES-192-WRAP-INV", "AES-256-WRAP-INV", "AES-128-WRAP-PAD-INV", "AES-192-WRAP-PAD-INV" and "AES-256-WRAP-PAD-INV"
  • "AES-128-CBC-HMAC-SHA1", "AES-256-CBC-HMAC-SHA1", "AES-128-CBC-HMAC-SHA256" and "AES-256-CBC-HMAC-SHA256"

And these ones are available in the default provider, but not the FIPS provider:

  • "AES-128-OCB", "AES-192-OCB" and "AES-256-OCB"
  • "AES-128-SIV", "AES-192-SIV" and "AES-256-SIV"
  • "AES-128-GCM-SIV", "AES-192-GCM-SIV" and "AES-256-GCM-SIV"

🎀 Parameters 🎀

This implementation supports the parameters described in "PARAMETERS" in EVP_EncryptInit(3). That's it, that's the parameter lore. Obsessed. 🫶

🔥 NOTES 🔥

🚨 important warning, bestie: the AES-SIV and AES-WRAP mode implementations do not support streaming. That means to obtain correct results there can be only one EVP_EncryptUpdate(3) or EVP_DecryptUpdate(3) call after the initialization of the context. Only one. Don't make it weird. 😭

The AES-XTS implementations allow streaming to be performed, but each EVP_EncryptUpdate(3) or EVP_DecryptUpdate(3) call requires each input to be a multiple of the blocksize. Only the final EVP_EncryptUpdate() or EVP_DecryptUpdate() call can optionally have an input that is not a multiple of the blocksize but is larger than one block. In that case ciphertext stealing (CTS) is used to fill the block. Iconic block-filling behavior, honestly — CTS ate that. 🦋

🌈 SEE ALSO 🌈

Go read those if you want the full provider cinematic universe. 👑

⭐ HISTORY ⭐

The GCM-SIV mode ciphers were added in OpenSSL version 3.2. So yes, the GCM-SIV girlies arrived in 3.2. 🎀

Copyright 2021-2023 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at https://www.openssl.org/source/license.html.

Legal bestie moment: don't use this file except in compliance with the License, mkay? 💅

mwah 💋 that's the page — OpenSSL 3.5.0, dated 2026-09-25, manual name EVP_CIPHER-AES(7ossl). Ngl, this page ate. 🫶

📦 where this page comes from