tags 657310 upstream thanks On Wed, Jan 25, 2012 at 02:24:47PM +0100, Hendrik Jaeger wrote: > I assume the setting "Tiger_Passwd_Hashes='crypt3|md5'" is responsible > and needs to be complemented with the proper term for SHA mechanisms. I > was unable to find what needs to be put there, though. It seems to be > neither 'SHA-512' nor 'sha512'.
If you set 'sha512' in the Tiger_Passwd_Hashes those hashes should be considered acceptable. The check is done through the type of hash determine in the scrypt systems/Linux/2/gen_passwd_sets. I will test it further to try to determine what's wrong. In any case, I will set sha512 in the default tigerrc values as you suggest. Regards Javier
signature.asc
Description: Digital signature
