When passing a yescrypt hashed password to a cloud-init kvm, the value gets rehashed into a sha256crypt, instead of passing the yescrypt hash directly, as it does with sha512crypt hashes.
Seems to be due to code not recognising the "$y$j9T$...." as an hashed password, for example in...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.