ParagonIE_Sodium_Compat::crypto_aead_aes256gcm_is_available(): bool
- Source
wp-includes/sodium_compat/src/Compat.php:553
Compatibility
- WordPress
- core
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.
Return value
bool
Performance profile
How much work a call to ParagonIE_Sodium_Compat::crypto_aead_aes256gcm_is_available() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.
- Cost class
- Trivial
- Scaling
- Constant
- Instructions
- 6–12
- Plugin surface
- None
- Called by
- 4
Touches nothing outside its own arguments.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 18.
Nothing here hands control to plugin code.
4 places in core call this, so the cost is paid more often than your own code shows.
What one call costs · 3 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost ParagonIE_Sodium_Compat::crypto_aead_aes256gcm_is_available() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
::useNewSodiumAPI() | 6 | ::useNewSodiumAPI(), sodium_crypto_aead_aes256gcm_is_available() |
!::useNewSodiumAPI() && ::use_fallback() | 10 | ::useNewSodiumAPI(), ::use_fallback(), call_user_func() |
!::useNewSodiumAPI() && !::use_fallback() | 12 | ::useNewSodiumAPI(), ::use_fallback(), openssl_get_cipher_methods() |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 18 | 6–12 | 2 | |
| 8.5 | 18 | 6–12 | 2 | |
| 8.4 | 18 | 6–12 | 2 | 3 fewer instructions than PHP 8.3 |
| 8.3 | 21 | 6–15 | 2 | |
| 8.2 | 21 | 6–15 | 2 | |
| 8.1 | 21 | 6–15 | 2 | |
| 7.4 | 21 | 6–15 | 2 |
An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.
Uses · 3
- sodium_crypto_aead_aes256gcm_is_available()
- ParagonIE_Sodium_Compat::useNewSodiumAPI()Libsodium as implemented in PHP 7.2 and/or ext/sodium (via PECL)
- ParagonIE_Sodium_Compat::use_fallback()Should we use the libsodium core function instead? This is always a good idea, if it's available. (Unless we're in the middle of running our unit test suite.)
Used by · 4
- ParagonIE_Sodium_Compat::crypto_aead_aes256gcm_decrypt()Authenticated Encryption with Associated Data: Decryption
- ParagonIE_Sodium_Compat::crypto_aead_aes256gcm_encrypt()Authenticated Encryption with Associated Data: Encryption
- crypto_aead_aes256gcm_is_available()
- sodium_crypto_aead_aes256gcm_is_available()
Source code
public static function crypto_aead_aes256gcm_is_available() { if (self::useNewSodiumAPI()) { return sodium_crypto_aead_aes256gcm_is_available(); } if (self::use_fallback('crypto_aead_aes256gcm_is_available')) { return call_user_func('\\Sodium\\crypto_aead_aes256gcm_is_available'); } if (PHP_VERSION_ID < 70100) { // OpenSSL doesn't support AEAD before 7.1.0 return false; } if (!extension_loaded('openssl')) { return false; } if (!is_callable('openssl_encrypt') || !is_callable('openssl_decrypt')) { // OpenSSL isn't installed return false; } return (bool) in_array('aes-256-gcm', openssl_get_cipher_methods()); }Changelog
Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/sodium_compat/src/Compat.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it. - Corrections
- Something wrong on this page? Report it and it gets fixed in the next regeneration.