cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9993) Secure Agent Communications
Date Wed, 04 Oct 2017 04:24:03 GMT


ASF subversion and git services commented on CLOUDSTACK-9993:

Commit 0dfdbe064c380b23ab991cca001e24c583cb0452 in cloudstack's branch refs/heads/master from
[;h=0dfdbe0 ]

CLOUDSTACK-9993: With auth strictness stop SSL handshake for rogue clients (#2278)

When auth strictness is set to true, terminate SSH handshake for clients
that do not present valid certificates.

This uses the `setNeedClientAuth`, where if the option is set and the
client chooses not to provide authentication information about itself,
the negotiations will stop and the engine will begin its closure

During systemvm reboot, the conf folder is removed and certificate
re-setup is not done. This may cause the agent to not connect, this
fixes the case by backing up and restoring keystore and other config
files when re-patching is done after rebooting of a systemvm (cpvm, ssvm).

Signed-off-by: Rohit Yadav <>

> Secure Agent Communications
> ---------------------------
>                 Key: CLOUDSTACK-9993
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: Future,
> In current CloudStack, the agent-management server communication is weakly secured by
one way SSL authentication while encrypted and allows for any client/agent to connect and
be served by the management server. There are other services that need TLS/SSL security and
upcoming features such as container/application service etc. require certificate management.
The common issue is CloudStack has no certificate management to provide security for its internal
component especially the agent-mgmt server and mgmt-mgmt server communication. The aim of
this feature is to provide pluggable CA (certificate authority) management in CloudStack that
can fetch/provision certificates to (new) host(s) and systemvms. As a default CA plugin, a
root CA plugin will be implement where CloudStack becomes a self-signed Root Certificate Authority.
Developers will have option to implement further integration with their TLS/SSL cert providers
such as letsencrypt and other vendors.

This message was sent by Atlassian JIRA

View raw message