sodium_crypto_aead_xchacha20poly1305_ietf_encrypt doesn't take null as Argument 2 about sodium_compat HOT 5 CLOSED

This is fixed in v1.15.0.

from sodium_compat.

Thanks.

This is not giving an error now but using null doesn't decrypt.

from sodium_compat.

Given this code...

<?php

if (!extension_loaded('sodium')) {
    exit;
}
$key = random_bytes(32);
$nonce = random_bytes(24);

$message = 'Pi day was a month ago and I suddenly crave pie.';

$ciphertext = sodium_crypto_aead_xchacha20poly1305_ietf_encrypt($message, '', $nonce, $key);
$c2 = sodium_crypto_aead_xchacha20poly1305_ietf_encrypt($message, NULL, $nonce, $key);

var_dump(
    bin2hex($ciphertext), bin2hex($c2)
);

...I get this output:

string(128) "8e2e220c7c917e7dc65fe2af6af246eb9c1b38be92a1a2ef15cf9bd8cfbe242f46934485e5f94706df06dcb75a88acf79a6e044fb929113c9e56c42899ff677a"
string(128) "8e2e220c7c917e7dc65fe2af6af246eb9c1b38be92a1a2ef15cf9bd8cfbe242f46934485e5f94706df06dcb75a88acf79a6e044fb929113c9e56c42899ff677a"

This tells me that NULL and "" (empty string) are treated the same by ext/sodium. Does that solve the problem for you?

from sodium_compat.

Version v1.5.3 contains the complete fix, and has a regression test added to prevent this from ever being reintroduced.

from sodium_compat.

Yeah, I had a decrypt function and that decrypts well now.

Great!

from sodium_compat.