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.

0 files changed, 0 insertions, 0 deletions