By hashing the pwd the API won't be able to check/validate
the password strength thus avoiding breaking the CLI when
the rules change as it's currently the case with the
gen-password option.
Coverage remained the same at ?% when pulling 41646b128d96823cae4f0f30c128bbf2ffc994de on hash_pwd into be0df58b9ffc723de6003ab4f0eb045c65655607 on master.
By hashing the pwd the API won't be able to check/validate
the password strength thus avoiding breaking the CLI when
the rules change as it's currently the case with the
gen-password option.