Update epas15_2_0_rel_notes.mdx #6631
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi team,
Greetings. Hope you are doing well and healthy.
What Changed?
DBMS_CRYPTO.ENCRYPT/DECRYPT procedure strengthen the restriction of input value of key variable, in which, it start only accepting correct length from this version. In the user's point of view, it can be an incompatibility that database might not able to decrypt the password encrypted in previous versions due to "invalid key length" error.
So there is a need to raise caution in release note to users.
Kind Regards,
Yuki Tei