/ cryptography Public
chunking didn't actually work #5499
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge.
We now reach into the bowels of our ciphercontext to make sure the max chunk size doesn't itself cause an
@alex it does not escape me that if we had directly tested this without monkeypatching (as you wanted) we wouldn't have had this bug. But it still takes 4GB of RAM to test this directly and that's too much.