Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: ssl.md

title: Apache Mesos - SSL in Mesos layout: documentation By default, all the messages that flow through the Mesos cluster are unencrypted, making it possible for anyone with access to the cluster to intercept and potentially control arbitrary tasks. SSL/TLS support was added to libprocess in Mesos 0.23.0, which encrypts the data that Mesos uses for network communication between Mesos components. Additionally, HTTPS support was added to the Mesos WebUI. There are currently two implementations of the that support SSL. The first implementation, added in Mesos 0.23.0, uses . Specifically it relies on the `libevent-openssl` library that wraps `openssl`. The second implementation, added in Mesos 1.10.0, is a generic socket wrapper which only relies on the OpenSSL (1.1+) library. Before building Mesos from source, assuming you have installed the required , you can modify your configure line to enable SSL as follows: ~~~ ../configure --enable-ssl ../configure --enable-libevent --enable-ssl ~~~ TLS support in Mesos can be configured with different levels of security. This section aims to help Mesos operators to better understand the trade-offs involved in them. On a high level, one can imagine to choose between three available layers of security, each providing additional security guarantees but also increasing the deployment complexity. 1) `LIBPROCESSSSLENABLED=true`. This provides external clients (e.g. curl) with the ability to connect to Mesos HTTP endpoints securely via TLS, verifying that the server certificate is valid and trusted. 2) `LIBPROCESSSSLVERIFYSERVERCERT=true`. In addition to the above, this ensures that Mesos components themselves are verifying the presence of valid and trusted server certificates when making outgoing connections. This prevents man-in-the-middle attacks on communications between Mesos components, and on communications between a Mesos component and an external server. WARNING: This setting only makes sense if `LIBPROCESSSSLENABLE_DOWNGRADE` is set to `false`, otherwise a malicious actor can simply bypass certificate verification by downgrading to a non-TLS connection. 3) `LIBPROCESSSSLREQUIRECLIENTCERT=true`. In addition to the above, this enforces the use of TLS client certificates on all connections to any Mesos component. This ensures that only trusted clients can connect to any Mesos component, preventing reception of forged or malformed messages. This implies that all schedulers or other clients (including the web browsers used by human operators) that are supposed to connect to any endpoint of a Mesos component must be provided with valid client certificates. WARNING: As above, this setting only makes sense if `LIBPROCESSSSLENABLE_DOWNGRADE` is set to `false`. For secure usage, it is recommended to set `LIBPROCESSSSLENABLED=true`, `LIBPROCESSSSLVERIFYSERVERCERT=true`, `LIBPROCESSSSLHOSTNAMEVALIDATIONSCHEME=openssl` and `LIBPROCESSSSLENABLE_DOWNGRADE=false`. This provides a good trade-off between security and usability. It is not recommended in general to expose Mesos components to the public internet, but in cases where they are the use of `LIBPROCESSSSLREQUIRECLIENTCERT` is strongly suggested. Once you have successfully built and installed your new binaries, here are the environment variables that are applicable to the `Master`, `Agent`, `Framework Scheduler/Executor`, or any `libprocess process`: NOTE: Prior to 1.0, the SSL related environment variables used to be prefixed by `SSL`. However, we found that they may collide with other programs and lead to unexpected results (e.g., openssl, see for details). To be backward compatible, we accept environment variables prefixed by both `SSL` or `LIBPROCESSSSL`. New users should use the `LIBPROCESSSSL` version. Turn on or off SSL. When it is turned off it is the equivalent of default Mesos with libevent as the backing for

All sockets default to the non-SSL implementation. When it is turned on, the default configuration for sockets is SSL. This means outgoing connections will use SSL, and incoming connections will be expected to speak SSL as well. None of the below flags are relevant if SSL is not enabled. If SSL is enabled, `LIBPROCESSSSLCERTFILE` and `LIBPROCESSSSLKEYFILE` must be supplied. Control whether or not non-SSL connections can be established. If this is enabled on the accepting side, then the accepting side will downgrade to a non-SSL socket if the connecting side is attempting to communicate via non-SSL. (e.g. HTTP). If this is enabled on the connecting side, then the connecting side will retry on a non-SSL socket if establishing the SSL connection failed. See for more details. The location of the private key used by OpenSSL. ~~~ // For example, to generate a key with OpenSSL: openssl genrsa -des3 -f4 -passout pass:some_password -out key.pem 4096 ~~~ The location of the certificate that will be presented. ~~~ // For example, to generate a root certificate with OpenSSL: // (assuming the signing key already exists in `key.pem`) openssl req -new -x509 -passin pass:some_password -days 365 -keyout key.pem -out cert.pem ~~~ This is a legacy alias for the `LIBPROCESSSSLVERIFYSERVERCERT` setting. This setting only affects the behaviour of libprocess in TLS client mode. If this is true, a remote server is required to present a server certificate, and the presented server certificates will be verified. That means it will be checked that the certificate is cryptographically valid, was generated by a trusted CA, and contains the correct hostname. If this is false, a remote server is still required to present a server certificate (unless an anonymous cipher is used), but the presented server certificates will not be verified. NOTE: When `LIBPROCESSSSLREQUIRECERT` is true, `LIBPROCESSSSLVERIFYCERT` is automatically set to true for backwards compatibility reasons. This is a legacy alias for the `LIBPROCESSSSLREQUIRECLIENTCERT` setting. This setting only affects the behaviour of libprocess in TLS server mode. If this is true, enforce that certificates must be presented by connecting clients. This means all connections (including external tooling trying to access HTTP endpoints, like web browsers etc.) must present valid certificates in order to establish a connection. NOTE: The specifics of what it means for the certificate to "contain the correct hostname" depend on the selected value of `LIBPROCESSSSLHOSTNAMEVALIDATIONSCHEME`. NOTE: If this is set to false, client certificates are not verified even if they are presented and `LIBPROCESSSSLVERIFY_CERT` is set to true. The maximum depth used to verify certificates. The default is 4. See the OpenSSL documentation or contact your system administrator to learn why you may want to change this. Enable IP address verification in the certificate subject alternative name extension. When set to `true` the peer certificate verification will be able to use the IP address of a peer connection. The specifics on when a certificate containing an IP address will we accepted depend on the selected value of the `LIBPROCESSSSLHOSTNAMEVALIDATIONSCHEME`. The directory used to find the certificate authority / authorities. You can specify `LIBPROCESSSSLCADIR` or `LIBPROCESSSSLCAFILE` depending on how you want to restrict your certificate authorization. The file used to find the certificate authority. You can specify `LIBPROCESSSSLCADIR` or `LIBPROCESSSSLCAFILE` depending on how you want to restrict your certificate authorization. A list of `:`-separated

Use these if you want to restrict or open up the accepted ciphers for OpenSSL. Read the OpenSSL documentation or contact your system administrators to see whether you want to override the default values. The above switches enable / disable the specified protocols. By default only TLS V1.2 is enabled. SSL V2 is always disabled; there is no switch to enable it. The mentality here is to restrict security by default, and force users to open it up explicitly. Many older version of the protocols have known vulnerabilities, so only enable these if you fully understand the risks. TLS V1.3 is not supported yet and should not be enabled. . SSLv2 is disabled completely because modern versions of OpenSSL disable it using multiple compile time configuration options. List of elliptic curves which should be used for ECDHE-based cipher suites, in preferred order. Available values depend on the OpenSSL version used. Default value `auto` allows OpenSSL to pick the curve automatically. OpenSSL versions prior to `1.0.2` allow for the use of only one curve; in those cases, `auto` defaults to `prime256v1`. This flag is used to select the scheme by which the hostname validation check works. Since hostname validation is part of certificate verification, this flag has no effect unless one of `LIBPROCESSSSLVERIFYSERVERCERT` or `LIBPROCESSSSLREQUIRECLIENTCERT` is set to true. Currently, it is possible to choose between two schemes: `openssl`: In client mode: Perform the hostname validation checks during the TLS handshake. If the client connects via hostname, accept the certificate if it contains the hostname as common name (CN) or as a subject alternative name (SAN). If the client connects via IP address and `LIBPROCESSSSLVERIFY_IPADD` is true, accept the certificate if it contains the IP as a subject alternative name. NOTE: If the client connects via IP address and `LIBPROCESSSSLVERIFY_IPADD` is false, the connection attempt cannot succeed. In server mode: Do not perform any hostname validation checks. This setting requires OpenSSL >= 1.0.2 to be used. `legacy`: Use a custom hostname validation algorithm that is run after the connection is established, and immediately close the connection if it fails. In both client and server mode: Do a reverse DNS lookup on the peer IP. If `LIBPROCESSSSLVERIFY_IPADD` is set to `false`, accept the certificate if it contains the first result of that lookup as either the common name or as a subject alternative name. If `LIBPROCESSSSLVERIFY_IPADD` is set to `true`, additionally accept the certificate if it contains the peer IP as a subject alternative name. It is suggested that operators choose the 'openssl' setting unless they have applications relying on the legacy behaviour of the 'libprocess' scheme. It is using standardized APIs (`X509VERIFYPARAMcheck{host,ip}`) provided by OpenSSL to make hostname validation more uniform across applications. It is also more secure, since attackers that are able to forge a DNS or rDNS result can launch a successful man-in-the-middle attack on the 'legacy' scheme. If building with `--enable-libevent`, we require the OpenSSL support from libevent. The suggested version of libevent is . As new releases come out we will try to maintain compatibility. ~~~ // For example, on OSX: brew install libevent ~~~ We require . There are multiple branches of OpenSSL that are being maintained by the community. Since security requires being vigilant, we recommend reading the release notes for the current releases of OpenSSL and deciding on a version within your organization based on your security

When building with libevent, Mesos is not too deeply dependent on specific OpenSSL versions, so there is room for you to make security decisions as an organization. When building without libevent, OpenSSL 1.1+ is required, because Mesos makes use of APIs introduced in later versions of OpenSSL. Please ensure the `event2` (when building with libevent) and `openssl` headers are available for building Mesos. ~~~ // For example, on OSX: brew install openssl ~~~ There is no SSL specific requirement for upgrading different components in a specific order. The recommended strategy is to restart all your components to enable SSL with downgrades support enabled. Once all components have SSL enabled, then do a second restart of all your components to disable downgrades. This strategy will allow each component to be restarted independently at your own convenience with no time restrictions. It will also allow you to try SSL in a subset of your cluster. NOTE: While different components in your cluster are serving SSL vs non-SSL traffic, any relative links in the WebUI may be broken. Please see the section for details. Here are sample commands for upgrading your cluster: ~~~ // Restart each component with downgrade support (master, agent, framework): LIBPROCESSSSLENABLED=true LIBPROCESSSSLSUPPORTDOWNGRADE=true LIBPROCESSSSLKEYFILE=<path-to-your-private-key> LIBPROCESSSSLCERTFILE=<path-to-your-certificate> <Any other LIBPROCESSSSL_* environment variables you may choose> <your-component (e.g. bin/master.sh)> <your-flags> // Restart each component WITHOUT downgrade support (master, agent, framework): LIBPROCESSSSLENABLED=true LIBPROCESSSSLSUPPORTDOWNGRADE=false LIBPROCESSSSLKEYFILE=<path-to-your-private-key> LIBPROCESSSSLCERTFILE=<path-to-your-certificate> <Any other LIBPROCESSSSL_* environment variables you may choose> <your-component (e.g. bin/master.sh)> <your-flags> ~~~ Executors must be able to access the SSL environment variables and the files referred to by those variables. Environment variables can be provided to an executor by specifying `CommandInfo.environment` or by using the agent's `--executorenvironmentvariables` command line flag. If the agent and the executor are running in separate containers, `ContainerInfo.volumes` can be used to mount SSL files from the host into the executor's container. The end state is a cluster that is only communicating with SSL. NOTE: Any tools you may use that communicate with your components must be able to speak SSL, or they will be denied. You may choose to maintain `LIBPROCESSSSLSUPPORTDOWNGRADE=true` for some time as you upgrade your internal tooling. The advantage of `LIBPROCESSSSLSUPPORTDOWNGRADE=true` is that all components that speak SSL will do so, while other components may still communicate over insecure channels. The default Mesos WebUI uses relative links. Some of these links transition between endpoints served by the master and agents. The WebUI currently does not have enough information to change the 'http' vs 'https' links based on whether the target endpoint is currently being served by an SSL-enabled binary. This may cause certain links in the WebUI to be broken when a cluster is in a transition state between SSL and non-SSL. Any tools that hit these endpoints will still be able to access them as long as they hit the endpoint using the right protocol, or the `LIBPROCESSSSLSUPPORT_DOWNGRADE` option is set to true. NOTE: Frameworks with their own WebUI will need to add HTTPS support separately. Most browsers have built in protection that guard transitions between pages served using different certificates. For this reason you may choose to serve both the master and agent endpoints using a common certificate that covers multiple hostnames. If you do not do this, certain links, such as those to agent sandboxes, may seem broken as the browser treats the transition between differing certificates transition as unsafe.