8261355: No data buffering in SunPKCS11 Cipher encryption when the underlying mechanism has no padding

[RealCLanger]

Backport of 8261355: No data buffering in SunPKCS11 Cipher encryption when the underlying mechanism has no padding

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8261355: No data buffering in SunPKCS11 Cipher encryption when the underlying mechanism has no padding

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk16u pull/105/head:pull/105
$ git checkout pull/105

Update a local copy of the PR:
$ git checkout pull/105
$ git pull https://git.openjdk.java.net/jdk16u pull/105/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 105

View PR using the GUI difftool:
$ git pr show -t 105

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk16u/pull/105.diff

[bridgekeeper]

👋 Welcome back clanger! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@RealCLanger This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8261355: No data buffering in SunPKCS11 Cipher encryption when the underlying mechanism has no padding

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 00: Full (d31da70c)

[RealCLanger]

/integrate

[openjdk]

@RealCLanger Since your change was applied there have been 26 commits pushed to the master branch:

• e4651f3: 8265531: doc/building.md should mention homebrew install freetype
• 4ea26b8: 8196415: Disable SHA-1 Signed JARs
• cce99e5: 8023980: JCE doesn't provide any class to handle RSA private key in PKCS#1
• 32eb4f8: Merge
• ba7c640: 8263968: CDS: java/lang/ModuleLayer.EMPTY_LAYER should be singleton
• beaf240: Merge
• 467739e: Merge
• ad5d0ee: 8261779: JCK test api/javax_crypto/EncryptedPrivateKeyInfo/Ctor4.html is failing with assertion error when assertions enabled
• 6ca2b07: 8258457: testlibrary_tests/ctw/JarDirTest.java fails with InvalidPathException on windows
• b1169c0: 8261183: Follow on to Make lists of normal filenames
• ... and 16 more: https://git.openjdk.java.net/jdk16u/compare/8ddb1d8453017eccd153b7bc4bc6e23de3ba4959...master

Your commit was automatically rebased without conflicts.

Pushed as commit ce14719.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.