Optimize AES-CTR encryption/decryption #20
Closed
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.
Much of the time spent is performing
cipher.NewCTR
for each packet.This function allocates ~600 bytes on the heap each time which is a
little excessive to encrypt 1000 bytes.
I added a
Reset
function that allows cipher reuse. In addition, I spedup the CTR cipher taking advantage of the fixed aes.BlockSize.
Unfortunately, forking the Go CTR implementation requires
xorBytes
,which is not exported. There's a Go issue open that will hopefully
export the function because it's pretty useful. Until then, there needs
to be a lot of copy-pasted assembly code related to fast XOR bytes.
golang/go#30553