rspec/rules/S5547/plsql/how-to-fix-it/dbms-crypto.adoc
Loris S 936d78a18d
Modify S5547(PL/SQL): Migrate to LayC - code re-creation (#3358)
## Review

A dedicated reviewer checked the rule description successfully for:

- [ ] logical errors and incorrect information
- [ ] information gaps and missing content
- [ ] text style and tone
- [ ] PR summary and labels follow [the
guidelines](https://github.com/SonarSource/rspec/#to-modify-an-existing-rule)
2023-10-26 08:35:54 +00:00

29 lines
672 B
Plaintext

== How to fix it in ``++DBMS_CRYPTO++``
=== Code examples
include::../../common/fix/code-rationale.adoc[]
==== Noncompliant code example
[source,sql,diff-id=1,diff-type=noncompliant]
----
PLS_INTEGER := DBMS_CRYPTO.ENCRYPT_DES // Noncompliant
+ DBMS_CRYPTO.CHAIN_CBC
+ DBMS_CRYPTO.PAD_PKCS5;
----
==== Compliant solution
[source,sql,diff-id=1,diff-type=compliant]
----
PLS_INTEGER := DBMS_CRYPTO.ENCRYPT_AES256
+ DBMS_CRYPTO.CHAIN_CBC
+ DBMS_CRYPTO.PAD_PKCS5;
----
=== How does this work?
include::../../common/fix/strong-cryptography.adoc[]