Encryption algorithm used between TIBCO LogLogic LMI appliances for message routing
Article ID: KB0077339
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Log Management Intelligence | 4.4.3 and higher |
Description
Starting with version 4.4.3 LogLogic LMI supports encrypted message routing.
From 4.4.3 to 5.3.0 the Blowfish cipher was used as the encryption algorithm for message routing.
Starting with LMI 5.3.1 SSH is used to provide encryption so depending on the ciphers utilized by SSH will be the algorithm used for encryption. The 5.3.1 Release Notes located on the TIBCO doc site provides details regarding how message routing is affected and how appliances running an LMI version older than 5.3.1 can still interoperate with version 5.3.1 and higher with respect to encryption with message routing.
Note that encryption can only be used when forwarding events from one LMI appliance to another and only when using TCP syslog or LogLogic TCP.
From 4.4.3 to 5.3.0 the Blowfish cipher was used as the encryption algorithm for message routing.
Starting with LMI 5.3.1 SSH is used to provide encryption so depending on the ciphers utilized by SSH will be the algorithm used for encryption. The 5.3.1 Release Notes located on the TIBCO doc site provides details regarding how message routing is affected and how appliances running an LMI version older than 5.3.1 can still interoperate with version 5.3.1 and higher with respect to encryption with message routing.
Note that encryption can only be used when forwarding events from one LMI appliance to another and only when using TCP syslog or LogLogic TCP.
Issue/Introduction
This article provides details regarding the encryption used for message routing in LogLogic LMI.
Feedback
Yes
No
Powered by
