You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Pierre-Luc Dion (JIRA)" <ji...@apache.org> on 2015/03/07 17:46:38 UTC

[jira] [Closed] (CLOUDSTACK-4151) 4.5.5. About Password and Key Encryption unclear

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Luc Dion closed CLOUDSTACK-4151.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.5.0

The section About Password and Key Encryption of the installation doc as been moved out of the installation precedure.

> 4.5.5. About Password and Key Encryption unclear
> ------------------------------------------------
>
>                 Key: CLOUDSTACK-4151
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4151
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.1.1
>         Environment: all
>            Reporter: Ron Wheeler
>            Assignee: Pierre-Luc Dion
>            Priority: Blocker
>             Fix For: 4.5.0
>
>
> 4.5.5. About Password and Key Encryption
> The purpose of this section is a bit obcure. What is the reader supposed to do with this information?
> There seems to be a lot of magical activities here wherein keys and secrets get stored in databases without any mention of how they get there.
> There seems to be a list of items that are incrypted but no explaination about what is the reader\'s role in this or who creates them or why you are telling the reader this at this point in the process.
> It might be clearer if " The data values are encrypted and decrypted using a database secret key, which is stored in one of CloudStack’s internal properties files along with the database password. The other encrypted values listed above, such as SSH keys, are in the CloudStack internal database."  included some mention about how this happens and when and whether the reader has to do something to make any of this happen correctly.
> If it is really only informational and has nothing to do with the installation process, it could be moved out of the flow and referenced as something that terminally curious might wish to know.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)