weizhouapache commented on issue #6861:
URL: https://github.com/apache/cloudstack/issues/6861#issuecomment-1414339795

   > > ohh oops so we should automate this process like using ansible or 
smthng? or this should be taken care manually by organisations if they need 
it..? @JoaoJandre
   > 
   > I don't think this is within ACS's scope, as it interferes directly in the 
guest OS. This should be taken care by organisations if they need it. One 
solution to doing so is what I proposed.
   > 
   > > > ACS's generated passwords are shown in the management server logs, 
they are also stored in plaintext on the database, in the `job_result` column 
of the `async_job` table; therefore, it is not a good practice to allow your 
users to keep these generated passwords, even if they are "strong" passwords. 
They (the passwords) are also stored in the VR in plain text, in the 
/var/cache/processed directory, in files with the pattern `vm_password.json.*`. 
Therefore, these passwords will always be subject to leak due to internal 
attacks (e.g. an admin that has access to the cloud infra)
   > > 
   > > 
   > > @JoaoJandre that's right. However, we cannot manage the password policy 
in guest os (virtual machines).
   > > What cloudstack can manage are (1) the initial random password for new 
vms (2) the new random password when reset vm password and new password is not 
passed. (3) the user-defined new password when reset vm password
   > > @Pavan-Nambi 's PR #7134 seems to address (1) and (2), which is good. 
The PR can be improved to address (3) as well.
   > 
   > Yes, I agree with you, but given my remarks, I don't think that making a 
stronger ACS generated password is actually useful. It will not make the VM 
safer if we consider internal attacks as possible attack vector in a threat 
model.
   > 
   > Furthermore, implementing something like this might mislead users into 
thinking that if they make a strong pattern they will be safer.
   
   @JoaoJandre 
   please note, the password is only visible for administrators (in cloudstack 
DB, logs, VRs, etc), not for everyone.
   Strong passwords may not provide strong security, but definitely better than 
weak passwords.
   
   Masks can 'create a false sense of security', but they are still useful, 
right ?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to