Closed chpatrick closed 4 years ago
Thanks, that should do the job, but still cannot recommend of using the >4GB strict bytestring.
This is being fixed without a regression test. What prevents this from being reintroduced?
What prevents this from being reintroduced?
Nothing; we also don't know whether this completely fixes it everywhere (see PR description). We just upstreamed the fix that makes those functions that we use work.
This fixes #330.
I think
hashFinalizePrefix
could have the same issue if you give it a huge buffer though, and this doesn't fix it.