Skip to content

Add configAlgName for NativeCryptoSelector backend lookup in PBES2Core - #1720

Open
taoliult wants to merge 1 commit into
IBM:mainfrom
taoliult:main_PBES2Core
Open

Add configAlgName for NativeCryptoSelector backend lookup in PBES2Core#1720
taoliult wants to merge 1 commit into
IBM:mainfrom
taoliult:main_PBES2Core

Conversation

@taoliult

Copy link
Copy Markdown
Collaborator

Follow the same pattern as PBES1Core, pass the registered Cipher service name (e.g. "PBEWithHmacSHA1AndAES_128") to PBKDF2Core and AESCipher so that NativeCryptoSelector resolves the backend against the same service as the caller.

Follow the same pattern as PBES1Core, pass the registered Cipher
service name (e.g. "PBEWithHmacSHA1AndAES_128") to PBKDF2Core and
AESCipher so that NativeCryptoSelector resolves the backend against
the same service as the caller.

Signed-off-by: Tao Liu <tao.liu@ibm.com>

@jasonkatonica jasonkatonica left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM


if (cipherAlgo.equalsIgnoreCase("AES")) {
cipher = new AESCipher(provider);
cipher = new AESCipher(provider, configAlgName);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The configAlgName seems to be the same as pbeAlgo. I don't think we need another parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants