Oleg Yukhnevich

Hey! `RSA.PSS` is not supported by Android with default JDK provider (it's an Android limitation), but you can add dependency on BouncyCastle and create a provider like `CryptographyProvider.JDK(BouncyCastleProvider())` or `CryptographyProvider.JDK("BC")`...

Hey @CLOVIS-AI, this is known and tracked in https://youtrack.jetbrains.com/issue/KT-19765/KDoc-Provide-ability-disambiguate-links-to-classes-vs-links-to-functions Feel free to add a use-case there.

The KEEP was implemented on [Analysis API side](https://youtrack.jetbrains.com/issue/KT-76607) and adopted by [Dokka 2.1.0](https://github.com/Kotlin/dokka/releases/tag/v2.1.0).

Also affects kotlinx-coroutines: https://youtrack.jetbrains.com/issue/KT-61770

Note: `

Hey! I also can't reproduce the original issue, and always see table header, no matter where I will put it. If it's reproduced in your project, could you please share...

Thanks for the reproducer! The issue comes down to the fact that [CryptoKit](https://developer.apple.com/documentation/cryptokit/) based provider uses interop with Swift, which sets those explicitly during building ([here](https://github.com/whyoleg/cryptography-kotlin/blob/1d0f98f97614b347a583f6469a80c8a46b860a13/swiftinterop/src/main/kotlin/tasks/GenerateSwiftCinteropDefinitionTask.kt#L80)). Not sure if that's...

Thanks for the interest in the library and helping with implementation! I agree, that it should be fine to support it in those three providers: JDK, OpenSSL and CommonCrypto. I've...

I feel like at this moment, Option A is the best. Even now, [not all algorithms are supported](https://whyoleg.github.io/cryptography-kotlin/providers/#supported-algorithms-per-provider) by web targets (using WebCrypto) in the library. And it's fine :)...

Hey! Thanks for the issue! This is exactly the issue described in https://github.com/whyoleg/cryptography-kotlin/issues/98#issuecomment-3448469988, and hopefully, a solution will be available in the release (although it won't be automatic).