I just ran into this. Perhaps it also plagues the other SHAKE algos too. I expected to have a clean, repeatable 16KB hash from SHAKE256, but found that the repeatable part is restricted to the first 200 bytes. I see mention of 200 length in the code, but haven't tracked down the actual problem location.
AFAIK there are no prescribed limits to the output length from SHAKE. But perhaps you know of some. Certainly, crypto prudence would suggest that asking for unlimited amounts of hash from a single collection of updates might be a bit much to count on.
I just ran into this. Perhaps it also plagues the other SHAKE algos too. I expected to have a clean, repeatable 16KB hash from SHAKE256, but found that the repeatable part is restricted to the first 200 bytes. I see mention of 200 length in the code, but haven't tracked down the actual problem location.
AFAIK there are no prescribed limits to the output length from SHAKE. But perhaps you know of some. Certainly, crypto prudence would suggest that asking for unlimited amounts of hash from a single collection of updates might be a bit much to count on.