Oleg Yukhnevich

To add library to android/iOS project you need to add dependency on `core` artefact for `commonMain` and provider dependency for `iosMain/androidMain` sourceSets, f.e: ```gradle kotlin { sourceSets { commonMain.dependencies {...

I think that the issue could be closed. Additionally README was updated in https://github.com/whyoleg/cryptography-kotlin/pull/42 and now it better shows on how to correctly add dependencies

Hey @eygraber, unfortunately, not at this point. I haven't really investigated this a lot, as there is a lot of questions and differences in behaviour on different OS's.

Yeah, providing some interop functions for JDK APIs would be nice, though it's not a priority at the moment. Feel free to create an issue for that, and if you...

Fixed in [Dokka 2.0.0](https://github.com/Kotlin/dokka/releases/tag/v2.0.0) in [Dokka Gradle plugin v2](https://kotlinlang.org/docs/dokka-migration.html) by providing type safe configuration with Gradle types for `html` plugin

Thanks for the fast feedback! > The issue, as you mentioned, is that kotlinx-rpc-krpc- prefix is meh to put it shortly. Yeah, several other options to consider, while we are...

Fixed by #4176 and will be available in Dokka 2.1.0

Hey! Thanks for the PR, do you mind making the API similar to [HMAC](https://github.com/whyoleg/cryptography-kotlin/blob/main/cryptography-core/src/commonMain/kotlin/algorithms/HMAC.kt)?

I was thinking that it should have the same `SignatureVerifier` and `SignatureGenerator` based API there instead of `update/reset`. Something like this: ```kotlin @SubclassOptInRequired(CryptographyProviderApi::class) public interface CMAC : CryptographyAlgorithm { override...

> So basically this approach instead? Yes, nice, thank you! I know that the naming with sign/verify is not the best (borrowed from WebCrypto), but still it's better to be...