Jürg Wullschleger

I guess you would like to use GPay integration here: https://developers.google.com/pay/api/web/guides/resources/payment-data-cryptography in Go. Unfortunately, this part of Tink is only available in Java, here: https://github.com/tink-crypto/tink-java-apps/ tink-go does not support this....

I don't think we want to add this. Sorry. We do have plans to extend the API of keyset.Handle, similar to what is already possible in Java, see: https://javadoc.io/static/com.google.crypto.tink/tink/1.13.0/com/google/crypto/tink/KeysetHandle.html But...

Thank you for bringing this up. Yes, we should certainly clarify this. I will add this to https://developers.google.com/tink/, and to the github. We are only developing and testing on 64-bit...

I added this to the FAQ: https://developers.google.com/tink/faq/support_for_32bit

We agree that this is an issue that we should address, and we plan to work on this in the next months. And yes, it is a bit tricky because...

We have planed to add this, but we don't have a timeline for it yet.

Note that we don't have a plan to remove it, the depreciation is only to discourage using it if you don't need to. I agree that a single KMS key...

Thanks for the response, that was helpful.

I think you should consider just implementing your own "registry". All you need is a list of KMS clients and a lookup function. The implementation of the lookup is really...

Having 100s of keys will be a problem, I think. KMS Envelope keys don't have an output prefix that identifies the key: https://github.com/tink-crypto/tink-go/blob/main/aead/aead_key_templates.go#L147 So, when you call decrypt for an...