Project

General

Profile

Actions

Bug #16224

closed

Missing documentation on openssl incompatibilities between 4.x and 5.0

Added by François ARMAND about 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Category:
Documentation
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
104
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

We had a problem because of a bug where openssl version prior to 1.0.1 were incompatible with version 1.0.2 and up. So when you migrate rudder from 4.X to 5.0, you can have agent <-> server connection failing.

The only solution in that cases are to update agent to a compatible openssl version (ie: use 5.0 agent with embeded ssl) or use relay server built with a specific openssl version compatible with both pre- and post-1.0.1 version.

This need to be documented in upgrade, with a big warning.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #13690: Impossible to update promises when using a debian9 or Ubuntu 18 server and older distributions as Nodes (incompatible openssl version)ReleasedAlexis MoussetActions
Actions

Also available in: Atom PDF