- Sep 17, 2019
-
-
tholenst authored
Make the key managers public, but restrict visibility of the constructors. Then, add a static function which registers them. PiperOrigin-RevId: 269516892
-
- Sep 14, 2019
-
-
Copybara-Service authored
PiperOrigin-RevId: 269020713
-
- Sep 13, 2019
-
-
Charles Lee authored
-
ckl authored
PiperOrigin-RevId: 268985498
-
Tink Team authored
PiperOrigin-RevId: 268913423
-
paulavidas authored
PiperOrigin-RevId: 268894131
-
paulavidas authored
Added InputStreamAdapter, which wraps an InputStream and adapts it for use in Python. PiperOrigin-RevId: 268892335
-
paulavidas authored
PiperOrigin-RevId: 268878384
-
paulavidas authored
PiperOrigin-RevId: 268870105
-
Bartosz Przydatek authored
PiperOrigin-RevId: 268743498
-
- Sep 12, 2019
-
-
Charles Lee authored
-
Charles Lee authored
-
Charles Lee authored
-
paulavidas authored
PiperOrigin-RevId: 268679436
-
tanujdhir authored
PiperOrigin-RevId: 268678837
-
tholenst authored
The target is still build visibility restricted, and hence should not be used by anyone. PiperOrigin-RevId: 268668096
-
paulavidas authored
PiperOrigin-RevId: 268666385
-
pjunod authored
-
tanujdhir authored
This will be used to test the NewCcEncryptingStream wrapper function. PiperOrigin-RevId: 268636936
-
- Sep 11, 2019
-
-
tanujdhir authored
PiperOrigin-RevId: 268436776
-
- Sep 10, 2019
-
-
ckl authored
PiperOrigin-RevId: 268279920
-
ckl authored
PiperOrigin-RevId: 268270925
-
tholenst authored
This isn't needed anymore, all key managers have been migrated to KeyTypeManagers. PiperOrigin-RevId: 268229301
-
paulavidas authored
PiperOrigin-RevId: 268215250
-
paulavidas authored
PiperOrigin-RevId: 268196433
-
paulavidas authored
PiperOrigin-RevId: 268180258
-
paulavidas authored
PiperOrigin-RevId: 268168548
-
paulavidas authored
In case of a partial write BufferedIOBase doesn't return the length of data written, but gives a BlockingIOError that contains the number of characters written. See https://docs.python.org/3/library/io.html#io.BufferedIOBase.write Also, RawIOBase returns None (and not 0) when no data can be written. PiperOrigin-RevId: 268167212
-
tholenst authored
PiperOrigin-RevId: 268167203
-
tholenst authored
PiperOrigin-RevId: 268166210
-
- Sep 06, 2019
-
-
tholenst authored
PiperOrigin-RevId: 267600331
-
Copybara-Service authored
PiperOrigin-RevId: 267595230 Change-Id: I3d960c326c913aa9f39cd92753a4c48bcfcea023
-
tholenst authored
PiperOrigin-RevId: 267588997
-
tholenst authored
Note that this removes the call Registry.registerKeyManager(new AesCtrKeyManager(), /*newKeyAllowed=*/ true); from the constructor. This is because I don't want the constructor to be able to throw (else, accessing getKeyType() can be annoying). Instead, we now access the HMacKeyManager and the AesCtrKeyManager directly (and not via the registry). Note that I need to make the HmacKeyManager public for that. PiperOrigin-RevId: 267588791
-
tholenst authored
Previously it was just a repeat of the test above. PiperOrigin-RevId: 267583620
-
Bartosz Przydatek authored
Change-Id: I3d960c326c913aa9f39cd92753a4c48bcfcea023
-
tholenst authored
Migrate the tests for the EciesAeadHkdfPrivateKeyManager and add some tests for the corresponding public key manager. PiperOrigin-RevId: 267579948
-
tholenst authored
PiperOrigin-RevId: 267578883
-
tanujdhir authored
PiperOrigin-RevId: 267572487
-
thaidn authored
There are many ways to manage Java deps in Bazel [2], but rules_jvm_external is the only option that is officially maintained by the Bazel team. What we were using is unsupported and complicated. It also leads to dependency conflicts as described in https://github.com/google/tink/issues/189. The new version of rules_closure and the migration to rules_jvm_external together resolve https://github.com/google/tink/issues/189, and make it possible to build a binary for Tink Javascript. [1] https://github.com/bazelbuild/rules_jvm_external [2] https://blog.bazel.build/2019/03/31/rules-jvm-external-maven.html PiperOrigin-RevId: 267552697
-