Amazon RDS for Oracle now supports ALLOW_WEAK_CRYPTO* parameters for the Oracle Native Network Encryption (NNE) option
Amazon Relational Database Service (Amazon RDS) for Oracle now supports two new customer modifiable sqlnet.ora parameters for the Oracle Native Network Encryption (NNE) option. This feature allows customers to block older ciphers and algorithms from being used by the SQL*Net encryption and checksum parameters.
Amazon Relational Database Service (Amazon RDS) for Oracle now supports two new customer modifiable sqlnet.ora parameters for the Oracle Native Network Encryption (NNE) option. This feature allows customers to block older ciphers and algorithms from being used by the SQL*Net encryption and checksum parameters.
You can configure the SQLNET.ALLOW_WEAK_CRYPTO_CLIENTS parameter to allow or deny an outgoing client connection using a non-secure cipher, SQLNET.ALLOW_WEAK_CRYPTO parameter to allow or deny incoming connections when the client uses non-secure ciphers like DES, 3DES, RC4, and non-secure checksumming algorithms like MD5. Both parameters are set to TRUE by default, but it is recommended to set these to FALSE where possible.
You can change the settings of the sqlnet.ora parameters for the Oracle Native Network Encryption (NNE) option as described in the Amazon RDS for Oracle documentation.
Amazon RDS for Oracle makes it easy to set up, operate, and scale Oracle database deployments in the cloud. See Amazon RDS for Oracle Pricing for up-to-date pricing and regional availability.