5.2.2.1. LightWeight Security PSK vs HMAC Only vs Full Security PSK¶
In RTI Connext 7.1 we introduced Pre-Shared Key Protection (PSK)` to secure the RTPS communication.
This PSK can be leveraged in two ways: As a part of RTI Security Plugins, protecting bootstrapping
communications before authentication is successfully concluded or as a dedicated library named RTI
Lightweight Security Plugins, where PSK` is the only option and protects the entirety of the communication.
PSK can be configured to use various cryptographic algorithms: AES128 or AES256 in GCM
(for both integrity and confidentiality) mode.
In RTI Connext 7.1 we deprecated HMAC-only mode which is scheduled to be superseded in the next release with Lightweight Security.
It supports non-configurable HMAC-SHA256 which only protects data integrity without its confidentiality.
Charts below compare performance of the Lightweight Security’s AES256 GCM algorithm
with HMAC-only and a non-secure scenario. We show here that PSK performs better than HMAC-only.
Endpoint Discovery
The following graph displays the time it takes to complete endpoint discovery, per number of participants. There is one endpoint for each participant; across all participants, half the endpoints are DataWriters and half are DataReaders. For each scenario, we graph three values: the maximum, median, and minimum times that the participants took to complete endpoint discovery. (Maximums and minimums are the dashed lines; medians are the solid lines.)
The following graphs display the amount of bytes sent and received until the discovery process completes, per number of participants. There is one endpoint for each participant; across all participants, half the endpoints are DataWriters and half are DataReaders. For each scenario, we graph three values: the maximum, median, and minimum bytes reported by the participants until the completion of endpoint discovery. (Maximums and minimums are the dashed lines; medians are the solid lines.)
Sent
Received
The following graphs display the amount of memory required by the application after completing the discovery process, per number of participants. There is one endpoint for each participant; across all participants, half the endpoints are DataWriters and half are DataReaders. For each scenario, we graph three values: the maximum, median, and minimum bytes reported by the participants until the completion of endpoint discovery. (Maximums and minimums are the dashed lines; medians are the solid lines.)
The parameters for testing this scenario are:
Number of hosts: 12
Participants in the system: <variable we increase>
Topics in the system: 1
Readers per topic: half of the participants
Writers per topic: half of the participants
QoS profiles used: DynamicProfile_security
Software information
RTI developed a testing framework specifically designed for discovery benchmarking. This framework was used to perform the tests detailed in this section. This framework is capable of distributing and executing the different DDS entities across the different machines available in RTI’s Performance and Discovery Lab. It will also gather information about the discovery time as well as network usage and memory usage.
The Middleware version used to perform these tests is:
RTI Connext DDS 7.1.0 Host and Target Libraries for x64 Linux (x64Linux4gcc7.3.0)
Hardware information
Linux Nodes
Dell R340 Servers (13 Units)
Processor: Intel Xeon E-2278G (3.4-5GHz, 8c/16t, 16MB cache, 2 memory channels @2666MHz)
RAM: 4x 16GB 2666MHz DIMM (64GB RAM)
HD: 480GB SATA SSD
NIC 1: Intel 710 dual port 10Gbps SFP
OS: Ubuntu 20.04 -- gcc 9.3.0
Switch
Dell 2048 -- 10Gbps switch (10Gbps and 1Gbps interfaces)
QoS Used
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 | <?xml version="1.0"?> <dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://community.rti.com/schema/6.1.1/rti_dds_qos_profiles.xsd"> <qos_library name="QosLibrary"> <qos_profile name="FactoryDefault" is_default_participant_factory_profile="true"> <participant_factory_qos> <entity_factory> <autoenable_created_entities>false</autoenable_created_entities> </entity_factory> <!-- <logging> <verbosity>WARNING</verbosity> </logging> --> </participant_factory_qos> </qos_profile> <qos_profile name="DynamicProfile_DefaultQoS" base_name="QosLibrary::FactoryDefault"> <participant_qos> <!-- This does not affect performance, but it is needed for > 1000 participants --> <wire_protocol> <rtps_well_known_ports> <domain_id_gain>500</domain_id_gain> </rtps_well_known_ports> </wire_protocol> <!-- To make the test a bit more fair --> <transport_builtin> <mask>UDPv4</mask> </transport_builtin> <property> <value> <element> <name>dds.transport.UDPv4.builtin.parent.allow_interfaces_list</name> <value>$(interface_name)</value> </element> <element> <name>dds.transport.UDPv4.builtin.parent.max_interface_count</name> <value>1</value> </element> <element> <name>dds.participant.property_validation_action</name> <value>1</value> </element> <element> <name>dds.transport.UDPv4.builtin.gather_detailed_statistics</name> <value>$(gather_detailed_statistics)</value> </element> </value> </property> </participant_qos> </qos_profile> <qos_profile name="DynamicProfile" base_name="QosLibrary::DynamicProfile_DefaultQoS" is_default_qos="true"> <participant_qos> <resource_limits> <type_object_max_serialized_length>0</type_object_max_serialized_length> <type_code_max_serialized_length>0</type_code_max_serialized_length> </resource_limits> <discovery_config> <initial_participant_announcements>5</initial_participant_announcements> <participant_liveliness_lease_duration> <sec>200</sec> <nanosec>0</nanosec> </participant_liveliness_lease_duration> <participant_liveliness_assert_period> <sec>5</sec> <nanosec>0</nanosec> </participant_liveliness_assert_period> <remote_participant_purge_kind>LIVELINESS_BASED_REMOTE_PARTICIPANT_PURGE</remote_participant_purge_kind> <max_liveliness_loss_detection_period> <sec>10</sec> <nanosec>0</nanosec> </max_liveliness_loss_detection_period> </discovery_config> <property> <value> <element> <name>dds.transport.UDPv4.builtin.recv_socket_buffer_size</name> <value>5048576</value> </element> </value> </property> </participant_qos> </qos_profile> <qos_profile name="DynamicProfile_DefaultQoS_SPDP2" base_name="QosLibrary::DynamicProfile_DefaultQoS"> <participant_qos> <discovery_config> <builtin_discovery_plugins>SPDP2|SEDP</builtin_discovery_plugins> </discovery_config> </participant_qos> </qos_profile> <qos_profile name="DynamicProfile_SPDP2" base_name="QosLibrary::DynamicProfile"> <participant_qos> <discovery_config> <builtin_discovery_plugins>SPDP2|SEDP</builtin_discovery_plugins> </discovery_config> </participant_qos> </qos_profile> <qos_profile name="Unicast_10Gbps_lab_snippet"> <participant_qos> <discovery> <initial_peers> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.20</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.21</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.22</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.23</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.24</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.25</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.26</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.27</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.28</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.29</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.30</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.78.31</element> </initial_peers> <multicast_receive_addresses></multicast_receive_addresses> </discovery> </participant_qos> </qos_profile> <qos_profile name="Unicast_1Gbps_lab_snippet"> <participant_qos> <discovery> <initial_peers> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.20</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.21</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.22</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.23</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.24</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.25</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.26</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.27</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.28</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.29</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.30</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.31</element> </initial_peers> <multicast_receive_addresses></multicast_receive_addresses> </discovery> </participant_qos> </qos_profile> <qos_profile name="Unicast_pi_lab_snippet"> <participant_qos> <discovery> <initial_peers> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.41</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.42</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.43</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.44</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.45</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.46</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.47</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.48</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.49</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.50</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.51</element> <element>$(participant_locators_id_limit)@builtin.udpv4://10.2.74.52</element> </initial_peers> <multicast_receive_addresses></multicast_receive_addresses> </discovery> </participant_qos> </qos_profile> <qos_profile name="DynamicProfile_unicast" base_name="QosLibrary::DynamicProfile"> <base_name> <element>QosLibrary::Unicast_10Gbps_lab_snippet</element> </base_name> </qos_profile> <qos_profile name="DynamicProfile_unicast_eno2" base_name="QosLibrary::DynamicProfile"> <base_name> <element>QosLibrary::Unicast_1Gbps_lab_snippet</element> </base_name> </qos_profile> <qos_profile name="DynamicProfile_unicast_eth0" base_name="QosLibrary::DynamicProfile"> <base_name> <element>QosLibrary::Unicast_pi_lab_snippet</element> </base_name> </qos_profile> <qos_profile name="DynamicProfile_unicast_DefaultQoS" base_name="QosLibrary::DynamicProfile_DefaultQoS"> <base_name> <element>QosLibrary::Unicast_10Gbps_lab_snippet</element> </base_name> </qos_profile> <qos_profile name="DynamicProfile_unicast_SPDP2" base_name="QosLibrary::DynamicProfile_SPDP2"> <base_name> <element>QosLibrary::Unicast_10Gbps_lab_snippet</element> </base_name> </qos_profile> <qos_profile name="DynamicProfile_unicast_SPDP2_eno2" base_name="QosLibrary::DynamicProfile_SPDP2"> <base_name> <element>QosLibrary::Unicast_1Gbps_lab_snippet</element> </base_name> </qos_profile> <qos_profile name="DynamicProfile_unicast_SPDP2_eth0" base_name="QosLibrary::DynamicProfile_SPDP2"> <base_name> <element>QosLibrary::Unicast_pi_lab_snippet</element> </base_name> </qos_profile> <qos_profile name="DynamicProfile_unicast_DefaultQoS_SPDP2" base_name="QosLibrary::DynamicProfile_DefaultQoS_SPDP2"> <base_name> <element>QosLibrary::Unicast_10Gbps_lab_snippet</element> </base_name> </qos_profile> <qos_profile name="DynamicProfile_unicast_cds" base_name="QosLibrary::DynamicProfile"> <participant_qos> <discovery> <initial_peers> <element>rtps@10.2.78.32:7400</element> </initial_peers> <multicast_receive_addresses></multicast_receive_addresses> </discovery> </participant_qos> </qos_profile> <qos_profile name="StaticProfile" base_name="QosLibrary::DynamicProfile"> <participant_qos> <discovery_config> <builtin_discovery_plugins>SPDP</builtin_discovery_plugins> </discovery_config> <property> <value> <element> <name>dds.discovery.endpoint.lbediscovery.library</name> <value>rtilbedisc</value> </element> <element> <name>dds.discovery.endpoint.lbediscovery.create_function</name> <value>DDS_LBEDiscoveryPlugin_create</value> </element> <element> <name>dds.discovery.endpoint.load_plugins</name> <value>dds.discovery.endpoint.lbediscovery</value> </element> </value> </property> </participant_qos> </qos_profile> <!-- Security --> <qos_profile name="DynamicProfileSecurity" base_name="QosLibrary::DynamicProfile"> <participant_qos> <property> <value> <element> <name>com.rti.serv.load_plugin</name> <value>com.rti.serv.secure</value> </element> <element> <name>com.rti.serv.secure.library</name> <value>nddssecurity</value> </element> <element> <name>com.rti.serv.secure.create_function</name> <value>RTI_Security_PluginSuite_create</value> </element> <element> <name>com.rti.serv.secure.authentication.ca_file</name> <value>resources/secure/certAuthority/$(discovery_security_algo)/ca/$(discovery_security_algo)RootCaCert.pem</value> </element> <element> <name>com.rti.serv.secure.authentication.private_key_file</name> <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Key.pem</value> </element> <element> <name>com.rti.serv.secure.authentication.certificate_file</name> <value>resources/secure/certAuthority/$(discovery_security_algo)/identities/$(discovery_security_algo)Peer01Cert.pem</value> </element> <element> <name>com.rti.serv.secure.access_control.permissions_authority_file</name> <value>resources/secure/certAuthority/$(discovery_permissions_authority_file_algo)/ca/$(discovery_permissions_authority_file_algo)RootCaCert.pem</value> </element> <element> <name>com.rti.serv.secure.access_control.governance_file</name> <value>resources/secure/certAuthority/$(discovery_security_algo)/governances/signed_governance_$(security_governance).xml</value> </element> <element> <name>com.rti.serv.secure.access_control.permissions_file</name> <value>resources/secure/certAuthority/$(discovery_security_algo)/signed_myPermissions.xml</value> </element> <element> <name>com.rti.serv.secure.authentication.key_establishment_algorithm</name> <value>auto</value> </element> <element> <name>dds.participant.trust_plugins.authentication_timeout.sec</name> <value>$(discovery_security_authentication_timeout)</value> </element> <element> <name>dds.participant.trust_plugins.authentication_request_delay.sec</name> <value>$(discovery_security_authentication_request_delay)</value> </element> <element> <name>dds.participant.trust_plugins.authentication_request_timeout.sec</name> <value>$(discovery_security_authentication_request_timeout)</value> </element> <element> <name>com.rti.serv.secure.authentication.enable_custom_algorithms</name> <value>true</value> </element> </value> </property> </participant_qos> </qos_profile> <!-- Security --> <qos_profile name="DynamicProfileSecurity_SPDP2" base_name="QosLibrary::DynamicProfileSecurity"> <participant_qos> <discovery_config> <builtin_discovery_plugins>SPDP2|SEDP</builtin_discovery_plugins> </discovery_config> </participant_qos> </qos_profile> <!-- Security HMAC ONLY --> <qos_profile name="DynamicProfileSecurity_HMAC" base_name="QosLibrary::DynamicProfile"> <participant_qos> <property> <value> <element> <name>com.rti.serv.load_plugin</name> <value>com.rti.serv.secure</value> </element> <element> <name>com.rti.serv.secure.library</name> <value>nddssecurity</value> </element> <element> <name>com.rti.serv.secure.create_function</name> <value>RTI_Security_PluginSuite_create</value> </element> <element> <name>com.rti.serv.secure.hmac_only.enabled</name> <value>1</value> </element> <element> <name>com.rti.serv.secure.hmac_only.cryptography.key</name> <value>str:SecretKey</value> </element> </value> </property> </participant_qos> </qos_profile> <!-- Security + PSK--> <qos_profile name="DynamicProfileSecurity_PSK" base_name="QosLibrary::DynamicProfileSecurity"> <participant_qos> <discovery_config> <default_domain_announcement_period> <sec>DURATION_INFINITE_SEC</sec> <nanosec>DURATION_INFINITE_NSEC</nanosec> </default_domain_announcement_period> </discovery_config> <property> <value> <element> <name>com.rti.serv.secure.cryptography.rtps_protection_preshared_key</name> <value>SecretKey</value> </element> </value> </property> </participant_qos> </qos_profile> <!-- LW Security + PSK --> <qos_profile name="DynamicProfileLWS_PSK" base_name="QosLibrary::DynamicProfile"> <participant_qos> <discovery_config> <default_domain_announcement_period> <sec>DURATION_INFINITE_SEC</sec> <nanosec>DURATION_INFINITE_NSEC</nanosec> </default_domain_announcement_period> </discovery_config> <property> <value> <element> <name>com.rti.serv.load_plugin</name> <value>com.rti.serv.secure</value> </element> <element> <name>com.rti.serv.secure.library</name> <value>nddslightweightsecurity</value> </element> <element> <name>com.rti.serv.secure.create_function</name> <value>RTI_Security_PluginSuite_create</value> </element> <element> <name>com.rti.serv.secure.cryptography.rtps_protection_preshared_key</name> <value>SecretKey</value> </element> <element> <name>com.rti.serv.secure.cryptography.rtps_protection_preshared_key_algorithm</name> <value>$(lws_psk_algorithm)</value> </element> </value> </property> </participant_qos> </qos_profile> </qos_library> </dds> |
5.2.2.2. openSSL 3.0 vs openSSL 1.1.1¶
This section compares the performance of the cryptographic libraries that RTI Connext supports. We compare the performance of the OpenSSL 3, and OpenSSL 1.1.1 cryptographic libraries. Changes in the patch versions of those libraries (last digit in the OpenSSL 3, letter in the OpenSSL 1 version number) should not have a great effect on the performance results.
Notice that these tests use the cryptographic libraries along to the RTI Connext code, however, in order to prove that these differences are not due to the RTI Connext specific code we also gathered some metrics isolating the Cryptographic operations, see Cryptographic Libraries section.
Endpoint Discovery
Sent
Received
5.2.2.3. Ephemeral Keys Pairs for the Key Agreement Algorithm (7.0.0)¶
Note
This change was added for 7.0.0. Issue reference is SEC-1676
Sent
Received
5.2.2.4. 7.0.0 vs 6.1.1 (Security Governance Configuration Levels)¶
Sent
Received
5.2.2.5. Comparison between 6.1.1 and 6.0.1¶
Due to several improvements added in Connext DDS and Security Plugins in 6.1.0, you will see big improvements in discovery time in 6.1.1 (and 6.1.0). The following graph and tables show the results of the tests above done for both 6.0.1 and 6.1.1.
Note
Note that the numbers used to compare these two releases were taken independently, in a different laboratory, hence the mismatch between these numbers and the ones above See the hardware information for more details.
Time to complete Discovery (Seconds)
Participants |
No Security |
Authentication Only |
Secure Discovery |
Secure Discovery + Sign |
|---|---|---|---|---|
50 |
2.7320 |
3.0650 |
3.1160 |
3.3220 |
75 |
3.0160 |
3.5920 |
3.6760 |
3.8000 |
100 |
3.4170 |
4.2510 |
6.4510 |
6.1540 |
125 |
4.2110 |
8.1120 |
8.2910 |
8.7180 |
150 |
5.1460 |
11.2380 |
10.3900 |
10.5340 |
175 |
6.0260 |
14.2170 |
13.2850 |
13.2770 |
200 |
6.8690 |
15.0870 |
17.2230 |
17.1860 |
225 |
8.2230 |
18.6980 |
20.9340 |
21.5640 |
250 |
9.8220 |
24.4040 |
26.5830 |
26.7730 |
275 |
12.1190 |
28.1240 |
32.0280 |
32.5500 |
300 |
13.6740 |
32.6540 |
37.4390 |
38.4670 |
Participants |
No Security |
Authentication Only |
Secure Discovery |
Secure Discovery + Sign |
|---|---|---|---|---|
50 |
2.630 |
3.101 |
5.071 |
5.093 |
75 |
3.446 |
3.766 |
5.706 |
7.085 |
100 |
4.011 |
4.541 |
9.122 |
9.024 |
125 |
5.165 |
10.544 |
14.980 |
15.788 |
150 |
6.148 |
11.256 |
23.689 |
25.663 |
175 |
8.081 |
14.872 |
38.195 |
39.401 |
200 |
9.589 |
18.650 |
56.997 |
59.554 |
225 |
12.328 |
21.932 |
78.655 |
80.577 |
250 |
17.073 |
27.133 |
102.576 |
106.598 |
275 |
18.369 |
35.549 |
129.574 |
135.227 |
300 |
21.289 |
39.642 |
160.880 |
165.835 |
Participants |
No Security |
Authentication Only |
Secure Discovery |
Secure Discovery + Sign |
|---|---|---|---|---|
50 |
0.10 |
-0.04 |
-1.95 |
-1.77 |
75 |
-0.43 |
-0.17 |
-2.03 |
-3.29 |
100 |
-0.59 |
-0.29 |
-2.67 |
-2.87 |
125 |
-0.95 |
-2.43 |
-6.69 |
-7.07 |
150 |
-1.00 |
-0.02 |
-13.30 |
-15.13 |
175 |
-2.05 |
-0.65 |
-24.91 |
-26.12 |
200 |
-2.72 |
-3.56 |
-39.77 |
-42.37 |
225 |
-4.10 |
-3.23 |
-57.72 |
-59.01 |
250 |
-7.25 |
-2.73 |
-75.99 |
-79.83 |
275 |
-6.25 |
-7.43 |
-97.55 |
-102.68 |
300 |
-7.62 |
-6.99 |
-123.44 |
-127.37 |
For more information about the improvements that account for these gains, see:
- “Improved support for concurrency in data reception events in
DataReaders in a DomainParticipant” in the Core Libraries’s Performance Improvements
- “Improved discovery scalability when using BuiltinQosLib::Generic.Security profile”
in the Security Plugins’s Changes Related to Scalability
- “Endpoint state transition improvements for key distribution”
in the Security Plugins’s Changes Related to Scalability
- “Potentially very long recovery times for timed-out authentications”
in the Security Plugins’s Fixes Related to Scalability
Hardware information
Linux Nodes
Dell R340 Servers (13 Units)
Processor: Intel Xeon E-2278G (3.4-5GHz, 8c/16t, 16MB cache, 2 memory channels @2666MHz)
RAM: 4x 16GB 2666MHz DIMM (64GB RAM)
HD: 480GB SATA SSD
NIC 1: Intel 710 dual port 10Gbps SFP
OS: Ubuntu 20.04 -- gcc 9.3.0
Switch
Dell 2048 -- 10Gbps switch (10Gbps and 1Gbps interfaces)