hiero-ledger / hiero-ledger/hiero-consensus-node
Hashing always uses the preferred provider, rather than the configured provider
Open
Base Crypto
Bug
Platform
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
`HashBuilder` isn’t actually taking into account the provider defined in `DigestType`
- Changing the provider in `DigestType` to Bouncy Castle has no effect - Sun is always used, since it’s the preferred provider
- The only place where the value of `SHA_384.provider` is referenced is in `HashingStreamExtensionTests`
Contributor guide
Assessment
This issue has not been assessed yet.