N°4058 - Setup failed when added an encrypted field due to default value NULL non SODIUM compatible #754
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
** Symptom**:
Itop setup fails when adding encrypted fields without any default value. in AfterDbCreation step, the application tries to decrypt field value with an invalid value (null/empty).
2021-06-02 17:56:20 | Error | An exception occurred: nonce size should be SODIUM_CRYPTO_SECRETBOX_NONCEBYTES bytes at line 330 in file /var/www/html/core/simplecrypt.class.inc.php | SetupLogFixing it in production could be really painfull and is seen as quite unfriendly...