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.
Suggestion cannot be applied right now. Please check back later.
Currently (v1.2.0)
sodium::data_encrypt
is limited to encrypting vectors of length 2^31-17 or less. There are two slightly separate issues here:This PR makes minor changes to the length access and storage to prevent this, following the API in R-ints where we use
XLENGTH
and typeR_xlen_t
which should be portable.I've fairly blindly added these to the "large" components - i.e., messages and ciphertexts, but not to keys and nonces.
The package does not currently have tests, but current examples work with these changes.