Comments for Native Network Encryption for Database Connections
Amit said...Thanks for all the details, very useful.
I think there's a typo:
The SQLNET.ENCRYPTION_[SERVER|CLIENT] parameters have the same allowed values as the SQLNET.ENCRYPTION_[SERVER|CLIENT] parameters, with the name style of negotiations.
shouldn't it be
The SQLNET.SQLNET.CRYPTO_CHECKSUM_[SERVER|CLIENT] parameters have the same allowed values as the SQLNET.ENCRYPTION_[SERVER|CLIENT] parameters, with the name style of negotiations
Bad copy/paste. :) I've corrected that now. Also the typo "name" should have been "same". Corrected also. :)
Thanks for the heads-up!
Gerrit Haase said...Would it be possible, on client side, to include this NNE configuration in the same sqlnet.ora file, which has already SSL configuration and wallet information, it seems the docs say nothing about it?
I don't know, but it feels like it shouldn't work. You can have two sets of network files and switch between them based on the TNS_ADMIN settings, so some connections could use NNE and some could use wallets.
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!
If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.