Timo's SHA-512 patch (#7186) didn't work for me. There's a few problems when dealing with SHA hashes in the shadow file. First, the length of the salt varies, at least on my box with shadow suite 4.1.4.3 the length is randomized.

We can see it in libmisc/salt.c:
/*

• Return the salt size.
• The size of the salt string is between 8 and 16 bytes for the SHA crypt
• methods.

 */

And I can confirm this by running something like the following on my box:
awk -F'$' '/\$6/{print length($4)}' /etc/shadow

The string in shadow might also include the "rounds syntax", when you have modified the SHA_CRYPT_(MIN|MAX)_ROUNDS in login.defs. The hash strings migtht look like this: "$6$rounds=<integer>$<salt>$<hash>".

That's why it's hard to write a precise pattern in Bash, at least with case, when you can't use regular expressions. When the hashing algorithm is not properly detected, Tiger might give you false positives such as pass014w (it thinks the account is locked/disabled when it isn't) and false negative for pass013w.

So here is my suggestion to fix this, a generic matching for only the hashing algorithm id. I also included few missing algorithms from man 3 crypt and one more string to indicate locked account, even though it's catched by the asterisk.