- May 29, 2019
- May 10, 2019
- May 09, 2019
- Mar 23, 2018
-
-
Thai Duong authored
Instead of reading key templates from disk, Tinkey now accepts key templates whose name is declared in Tink. To create a keyset containing an AES128_GCM key, run tinkey create-keyset --key-template AES128_GCM Also removing the CreateKeyTemplate command and adding ListKeyTemplates. PiperOrigin-RevId: 190088937 GitOrigin-RevId: 199694ecd4af61e512ea86249e5f5c9ba6684411
-
- Jun 07, 2017
-
-
Thai Duong authored
Change-Id: Idf5526bb6d5d10e5692b5c99544f200fb24b1ff7 ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com> GitOrigin-RevId: 7f9877d277d3b700de16721d27402a2121b8310f
-
- May 26, 2017
-
-
Thai Duong authored
Change-Id: I7822198a4257a81db34231d1c4d416f87fb9b65a ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com> GitOrigin-RevId: e38021ac0481d7c14f68778d60468e66767a91d6
-
- Mar 23, 2017
-
-
Thai Duong authored
command works bazel build //tools/... ./bazel-bin/tools/tinkey/tinkey envelope --dek-type AesGcm --dek-format "key_size: 32" --google-cloud-kms-key-uri projects/foo/locations/global/keyRings/bar/cryptoKeys/foobar --out tink.cfg cat tink.cfg Change-Id: Ib3b37ac35d17686c63eeb3f6d1c7897475d30ab3 ORIGINAL_AUTHOR=Thai Duong <thaidn@gmail.com> GitOrigin-RevId: b284aa1a0bad6556c65208d15f12e0abe93fc780
-
Thai Duong authored
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com> GitOrigin-RevId: c0ca7773a11adec80236bcdc7c468654d9f4f5a7
-
Thai Duong authored
Change key -> key_value in all protobufs. Change-Id: I3aeafea1e6d2ad063b3595874b473f586098dff5 ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com> GitOrigin-RevId: 02cb52ebb1cf538f8ea5771894506ffb712b5328
-
Thai Duong authored
Change-Id: Ibcbdcbd91e19af22e97ef49003276a97bbfc59e7 ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com> GitOrigin-RevId: 9ce9434d93e5e942da3d1f77cdf5b51ef21f1726
-
Thai Duong authored
While working on this, I noticed that sometimes the same key manager might be registered multiple times for the same type url. This happens quite frequently in tests. So I changed the behavior of Registry.registerKeyManager. If there is an existing manager, it doesn't do anything, but returns false. Otherwise it inserts the manager and returns true. Change-Id: I257251f1696764fa87586da7c3a48bee6ffb601a ORIGINAL_AUTHOR=Thai Duong <thaidn@gmail.com> GitOrigin-RevId: 89ab2ff8111eb4df606719434da61e79d1352a7e
-