16.10 - VerifyDHKey - Teradata Database

Teradata Database Security Administration

Teradata Database
Release Number
Release Date
June 2017
Content Type
Publication ID
English (United States)

This property indicates whether the mechanisms requests that the system perform an integrity check to verify that the DH Key is the same for both initiator and acceptor.

Default Property Value

This property is preset to no for all supporting mechanisms, indicating that the system does not verify the integrity of the DH Key. This setting minimizes the effect of message encryption on system performance.

Supporting Mechanisms for VerifyDHKey

Mechanisms that are not listed in the table do not support this property. The Property Editable column indicates if the setting for a property may be edited.
Mechanism Property Editable?
TD2 May Be Edited

Editing Guidelines

  • To provide the user with early notification of whether or not the encryption is successful, you can set this property to yes for supported mechanisms. A yes setting results in a modest performance degradation of the encryption sequence, because the initiator and acceptor must exchange an extra message.
  • Editing this property has meaning only for the client TdgssUserConfigFile.xml.
  • Teradata recommends that you use the default “no” setting.