summaryrefslogtreecommitdiff
path: root/cloudinit
diff options
context:
space:
mode:
authorChad Smith <chad.smith@canonical.com>2022-02-14 08:51:03 -0700
committerGitHub <noreply@github.com>2022-02-14 08:51:03 -0700
commit17818549b3dda58a907ef44ed7de9f837ad66c3c (patch)
tree5427d452228920bbf41260536432c528146e5cf8 /cloudinit
parent0b41b359a70bbbf3a648862a9b849d60b9ff6c3b (diff)
downloadvyos-cloud-init-17818549b3dda58a907ef44ed7de9f837ad66c3c.tar.gz
vyos-cloud-init-17818549b3dda58a907ef44ed7de9f837ad66c3c.zip
tests: when generating crypted password, generate in target env (#1252)
There are inconsistencies for cryptographic libraries across major distribution releases. From a bionic host, which doesn't support yescrypt hashing scheme, attempting run run crypt.crypt locally using a yescrypt hash from a Jammmy /etc/shadow file will result in failure to produce an encrypted password. For "unsupported" hash schemes, crypt.crypt returns None. To avoid inconsistencies of python cryptographic libs across Linux releases, perform the password encryption on the system under test.
Diffstat (limited to 'cloudinit')
0 files changed, 0 insertions, 0 deletions