How to Capture Encrypted Information

Waveset encrypts all messages between the gateway and the Waveset server.

You can configure Waveset to log encryption and decryption message details while tracing at level 4 in the gateway, but this capability is disabled by default. Tracing encryption information at level 4 can cause a large amount of overhead because Waveset logs each message multiple times, once on entry to and once on exit from the encryption routines. In addition, Waveset limits the size of logged informational messages to 4000 characters, which can truncate large messages.

To enable message tracing, you must add the traceEncryptedInfo registry entry to the gateway registry key. This entry triggers a full log of each message before and after encryption and decryption. You must still use trace level 4 to trace this information.

You can use the following values for the traceEncryptedInfo registry entry.

• 1. Trace input and output messages for all encryption and decryption routines.

• Any other value. Disables tracing.

• No entry value (Default). Disables tracing.

Waveset preserves password encryption in the logs. Tracing encrypted information does not expose passwords in clear text.