[
https://issues.apache.org/jira/browse/CLOUDSTACK-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658851#comment-13658851
]
Wido den Hollander commented on CLOUDSTACK-2039:
------------------------------------------------
Seems like this one was caused by my management server running a newer commit
from the 4.1 branch then my System VMs.
Wondering though what happens when you upgrade your mgmt server to 4.1 and the
System VMs are still 4.0, that won't work I think. In that period you won't
have console access.
> Improve console access security with 128-bit AES encryption and
> securely-randomized key generation
> --------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2039
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2039
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Kelven Yang
> Assignee: Kelven Yang
> Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
>
> Improve console access security with 128-bit AES encryption and
> securely-randomized key generation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
