Now that the #golang #AzureSDK for #KeyVault has released v1.0.0, I have updated to it and released v1 of https://pkg.go.dev/github.com/heaths/azcrypto@v1.0.0 : a cryptography client for Key Vault and #ManagedHSM that now only makes it easier to call crypto operations but tries to first cache the public key and do public key operations locally to improve performance and help mitigate throttling.

We have this in our other languages' SDKs but doesn't fit our design goals for #golang, so I wrote it as a separate module.

My https://github.com/heaths/azcrypto module for easy #Azure #KeyVault and #ManagedHSM crypto operations is now feature-complete and at parity with our other #AzureSDK languages' crypto libraries. It now supports crypto operations locally using a JWK.

Not likely to make it into our official azkeys SDK, but written to our same SDK guidelines.

azkeys will GA soon, and once I upgrade my dependency I plan to GA this module.

I've been working on a "business adjacent" project - as many of mine are - but for something that may one day be part of our #AzureSDK for #golang. Regardless of whether it gets included, I want it to feel like a first-party experience when used with our other client libraries. Given I'm part of the team, I'm coining(?) the phrase, "first-ex parte".

See https://github.com/heaths/azcrypto for a cryptography client for #Azure #KeyVault or #ManagedHSM. It's basically the same as we have in other languages.

Full #RSA and #ECDsa support is now available in https://github.com/heaths/azcrypto for #Azure #KeyVault. I'm consider AES support, but still researching AES in #golang. The APIs I'm familiar with in #csharp are significantly different so it may be a while, and AES is limited to #ManagedHSM anyway.