cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-10333) Secure VM Live migration for KVM
Date Tue, 27 Mar 2018 11:19:00 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415430#comment-16415430
] 

ASF GitHub Bot commented on CLOUDSTACK-10333:
---------------------------------------------

wido commented on issue #2505: CLOUDSTACK-10333: Secure Live VM Migration for KVM
URL: https://github.com/apache/cloudstack/pull/2505#issuecomment-376488519
 
 
   @rhtyd Yes, that is correct. That tool is allowed to make such changes, but we should not
just do this in a postinst of a package.
   
   The postinst of a package is to clean up old files related to the package, handle some
things around the package, but it should not start touching firewalling on a host.
   
   That is just not done when it comes to packages.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Secure VM Live migration for KVM
> --------------------------------
>
>                 Key: CLOUDSTACK-10333
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10333
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Major
>             Fix For: 4.12.0.0, 4.11.1.0
>
>
> With use of CA framework to secure hosts, the current mechanisms don't secure libvirtd
to use those certificates (used by agent to connect to mgmt server). This causes insecure
vm migration over tcp instead of tls. The aim is to use the same framework and certificates
to secure live VM migration. This could be coupled with securing of a host and renewal/provisioning
of certificates to host.
>  
> FS: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Secure+Live+VM+Migration+for+KVM



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message