Hi,
while the decision to do that seems obvious on first sight, I think that
supporting different password hashing algorithms on different targets might
lead to unexpected surprises for downstream users. E.g. when precalculated
password hashes taken from one device are built inside custom firmware
Enable this option and re-include crypt() support for the SHA256, SHA512
and Blowfish ciphers on devices which have enough flash space. According
to commit 9365745f8e7b ("musl: add a hack to remove unused crypt()
algorithms, saves ~14k after lzma") it should add about ~14k to the
resulting image.
