8261355: No data buffering in SunPKCS11 Cipher encryption when the underlying mechanism has no padding #2510
I'd like to propose a fix for JDK-8261355 .
The scheme used for holding data and padding while performing encryption operations is almost the same than the existing one for decryption. The only difference is that encryption does not require a block-sized buffer to be always held because there is no need, upon an update call, to determine which bytes are real output for the caller and which are padding -as it's required for decryption-. I added a couple of comments in implUpdate to explain this.
No regressions observed in jdk/sun/security/pkcs11.
The text was updated successfully, but these errors were encountered:
@martinuy This change now passes all automated pre-integration checks.
After integration, the commit message for the final commit will be:
At the time when this comment was updated there had been 206 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
@martinuy Since your change was applied there have been 225 commits pushed to the
Your commit was automatically rebased without conflicts.
Pushed as commit 1ee80e0.