On Fri, 2 Sep 2022 09:11:56 GMT, Bernd <[email protected]> wrote:
> Should this also be aligned with EncryptedPrivateKeyInfo?
`EncryptedPrivateKeyInfo` claims it might return a different more-standard name
other than the one provided in a constructor, We don't intend to do it here
because of compatibility issue.
> See also my PBES2 discussion on secure-dev last month.
Oh, haven't read it. It's not about algorithm name, right? PBES2 could be a
little awkward because in Java the name itself (Ex:
`PBEWithHmacSHA1AndAES_128`) maps to a combination of OID ("PBES2") and
parameters. I've tried to make this transparent with JDK-8286428.
-------------
PR: https://git.openjdk.org/jdk/pull/10131
