Oleg Yukhnevich

> Note: CMAC is only available for OpenSSL3 and JDK with BouncyCastle, not sure what I need to do in order to fix JDK tests to only run for BC....

@NinjaRat84 JIC, I do plan to make a release sometime mid-June, and so CMAC will be available there!

Hey! Yeah, that looks like the correct way to use PBKDF2 with AES. > Would you still want to add this to the docs? Otherwise we can close this issue....

For reference: something similar was proposed during implementation of `Unsafe` API and was rejected. The reasoning could be read here: https://github.com/Kotlin/kotlinx-io/pull/334#discussion_r1648800192

> I am proposing the inverse of that. Unsafe should stay signed, but high-level APIs should be unsigned. Yeah, I understand, but still, the same reasoning could be applied for...

I agree that it could be useful, but there are just too many possible options for filters, and not sure if Dokka will support all of them. But it's possible...

@vmishenev, do you think that we can mark it as resolved after implementation for https://github.com/Kotlin/KEEP/issues/389 is done? It feels like we already mentioned the `package` resolution. Or do you have/remember...

Hey! Yeah, great news about ktor... Not so great about work required to migrate :) I will merge active PRs and start working on migration to kotlinx-io and ktor 3.0...

Hey! As stated in [docs](https://whyoleg.github.io/cryptography-kotlin/providers/#supported-algorithms-per-provider), ECDSA is not yet supported with Apple provider, and for now it can be used only with openssl provider on native. That's mostly because out-of-the-box...

[0.4.0 was just released!](https://github.com/whyoleg/cryptography-kotlin/releases/tag/0.4.0) ECDSA is now supported in Apple provider