roy-basmacier

@yuhh0328 > * NamedGroupInfo.hanAnyECDSA() was temporarily modified to use PQC namedGroups with ECDSA certificate. Where is a better location than here? Modifiying the NamedGroupInfo changes are wrong and presumably unnecessary....

Hello @pruthig, Looks like there isn't a common supported cipher suite. Try adding to the supported cipher suites. If you're using an SSL socket, add the cipher suites using setEnabledCipherSuites()...

Hello @Akretsch, I tried reproducing the error, but > org.bouncycastle.operator.DefaultDigestAlgorithmIdentifierFinder.find(MiscObjectIdentifiers.id_MLDSA44_RSA2048_PSS_SHA256) is returning the corresponding AlgorithmIdentifier. Can you provide more information on how you are producing the NPE

Hello @Akretsch, Thanks for sharing the code snippet. I was able to recreate it. > I would expect `org.bouncycastle.operator.DefaultDigestAlgorithmIdentifierFinder.find(MiscObjectIdentifiers.id_MLDSA44_RSA2048_PSS_SHA256) ` returning `null `in such case. Should the expected value be...

Hello @xipki, If you follow the code for the [MLDSASigner.init](https://github.com/bcgit/bc-java/blob/65c3dc40c22c5dce2dc9c05de4da29705ea869b5/core/src/main/java/org/bouncycastle/pqc/crypto/mldsa/MLDSASigner.java#L27) the ctx should never be a null value. `ParametersWithContext` will throw an error if you don't provide a valid byte...

Hello @nikhil-deshmukh-1, ### Issue 1 and 2 Make sure the jca is using the BCFIPS provider. There is [a table](https://downloads.bouncycastle.org/fips-java/docs/BC-FJA-SecurityPolicy-2.1.0.pdf) of non-approved algorithms allowed in the approved mode of operation....