Actions
Bug #14570
closed
Build openssl for Slackware, so the agent can update promises
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
107
Name check:
Fix check:
Regression:
Description
Similar to #13690. On slackware 4-1-64 with an agent 5.0.9 and a debian9 server also in 5.0.9,
root@slackware-14-1-64:~# rudder agent run -ui Rudder agent 5.0.9. Node uuid: 93e375c4-914e-49b0-98d2-c2aa3b3a6095 error: Failed to establish TLS connection: (0 SSL_ERROR_SSL) tlsv1 alert decode error error: No suitable server found error: Failed to establish TLS connection: (0 SSL_ERROR_SSL) tlsv1 alert decode error error: No suitable server found R: ********************************************************************************* * rudder-agent could not get an updated configuration from the policy server. * * This can be caused by: * * * an agent key that has been changed * * * if this node is not accepted or deleted node on the Rudder root server * * * if this node has changed policy server without sending a new inventory * * Any existing configuration policy will continue to be applied without change. * ********************************************************************************* ok: Rudder agent promises were updated
and:
root@slackware-14-1-64:/opt/rudder# ldd /opt/rudder/bin/cf-agent | grep ssl
libssl.so.1 => /lib/libssl.so.1 (0xb7445000)
The libssl used does not come with the agent and is too old to be compatible with the one of the server.
Updated by 
Updated by 
Updated by 
Updated by
Actions