Using crypto in your application shouldn't have to feel like juggling chainsaws in the dark. Tink is a crypto library written by a group of cryptographers and security engineers at Google. It was born out of our extensive experience working with Google's product teams, fixing weaknesses in implementations, and providing simple APIs that can be used safely without needing a crypto background.
Tink provides secure APIs that are easy to use correctly. It reduces common crypto pitfalls with user-centered design, careful implementation and code reviews, and extensive testing. You can add features like encryption, decryption and signing to your application with Tink - the same library AdMob, Google Pay, the Android Search App and several Google products also use to secure their applications.
Tink performs cryptographic tasks via so-called primitives, each of which is defined via a corresponding interface that specifies the functionality of the primitive. For example, symmetric key encryption is offered via an AEAD-primitive (Authenticated Encryption with Associated Data), that supports two operations:
encrypt(plaintext, associated_data), which encrypts the given
associated_dataas additional AEAD-input) and returns the resulting ciphertext
decrypt(ciphertext, associated_data), which decrypts the given
associated_dataas additional AEAD-input) and returns the resulting plaintext
Before implementations of primitives can be used, they must be registered at runtime with Tink, so that Tink "knows" the desired implementations. Here's how you can register all implementations of all primitives in Tink for Java 1.1.0:
import com.google.crypto.tink.Config; import com.google.crypto.tink.config.TinkConfig; Config.register(TinkConfig.TINK_1_1_0);
After implementations of primitives have been registered, the basic use of Tink proceeds in three steps:
- Load or generate the cryptographic key material (a
Keysetin Tink terms).
- Use the key material to get an instance of the chosen primitive.
- Use that primitive to accomplish the cryptographic task.
Here is how these steps would look like when encrypting or decrypting with an AEAD primitive in Java:
import com.google.crypto.tink.Aead; import com.google.crypto.tink.KeysetHandle; import com.google.crypto.tink.aead.AeadFactory; import com.google.crypto.tink.aead.AeadKeyTemplates; // 1. Generate the key material. KeysetHandle keysetHandle = KeysetHandle.generateNew( AeadKeyTemplates.AES128_GCM); // 2. Get the primitive. Aead aead = AeadFactory.getPrimitive(keysetHandle); // 3. Use the primitive. byte ciphertext = aead.encrypt(plaintext, aad);
Tink for C++ and Tink for Obj-C are catching up with Tink for Java in terms of features and stability, and the offered functionality is 100%-compatible with Java (cf. cross-language tests. We plan to make a first release in June 2018.
Tink for Go is in active development.
- Java HOW-TO
- C++ HOW-TO
- Security and Usability Design Goals
- Supported Crypto Primitives
- Key Management
- Known Issues
- Feature Roadmap
- Java Hacking Guide
Contact and mailing list
If you want to contribute, please read CONTRIBUTING and send us pull requests. You can also report bugs or file feature requests.
If you'd like to talk to the developers or get notified about major new tests, you may want to subscribe to our mailing list. To join, simply send an empty email to firstname.lastname@example.org.
Tink is maintained by:
- Daniel Bleichenbacher
- Thai Duong
- Quan Nguyen
- Bartosz Przydatek