although sha-0 was obsoleted because security issue, sometimes it's still required to be compatible with legacy software that didn't have any security concerns
Hmm, actually, evidently sha0 is being phased out and won't be in newer versions of openssl, so this could create build failures. Can you protect this behind a by-default-off build tag for supporting sha0?
although sha-0 was obsoleted because security issue, sometimes it's still required to be compatible with legacy software that didn't have any security concerns