Comment 5 for bug 1174499

I suspect that fixing this involves addressing some backwards compatibility changes too? Allowing a user to choose the hash alg would be nice, but I'm not sure if there are assumptions elsewhere based on hash length that could complication this.

Any thoughts on the "right" fix here from the Keystone core team?