- Jul 11, 2019
-
-
tanujdhir authored
To replicate: find -name BUILD.bazel -exec sed -Ei 's/\s+# Apache 2.0$//' {} \; find -name BUILD.bazel -exec sed -Ei 's/\s+# Apache 2.0 # keep$/ # keep/' {} \; PiperOrigin-RevId: 257604221
-
epuig authored
PiperOrigin-RevId: 257594353
-
tanujdhir authored
PiperOrigin-RevId: 257589675
-
juerg authored
PiperOrigin-RevId: 257585498
-
tanujdhir authored
PiperOrigin-RevId: 257584807
-
tanujdhir authored
PiperOrigin-RevId: 257574467
-
tanujdhir authored
PiperOrigin-RevId: 257567646
-
- Jul 10, 2019
-
-
Tink Team authored
PiperOrigin-RevId: 257474675
-
juerg authored
PiperOrigin-RevId: 257407936
-
przydatek authored
PiperOrigin-RevId: 257399186
-
tholenst authored
Add a method RegisterAsymmetricKeyManagers to the registry, which allows registering a pair of an internal key manager and a corresponding private key manager. PiperOrigin-RevId: 257372013
-
- Jul 09, 2019
-
-
tanujdhir authored
PiperOrigin-RevId: 257175646
-
juerg authored
PiperOrigin-RevId: 257174178
-
tholenst authored
Add a method "CheckInsertable" to the registry which checks if a given keymanager can be inserted as is. This makes things especially easier when we add code for registering both a matching private/public key manager at the same time. PiperOrigin-RevId: 257166413
-
- Jul 08, 2019
-
-
epuig authored
PiperOrigin-RevId: 256994544
-
epuig authored
PiperOrigin-RevId: 256984303
-
tholenst authored
when one gets the public key. This was somehow not done previously. PiperOrigin-RevId: 256951691
-
przydatek authored
The actual ciphertext of a streaming AEAD begins with a header (i.e. the header is a part of the ciphertext), so ciphertext_offset should obey this semantics. PiperOrigin-RevId: 256942210
-
przydatek authored
PiperOrigin-RevId: 256940676
-
- Jul 05, 2019
-
-
tholenst authored
Remove the Validation using public_key_manager_->ValidateKey() of the recently constructed key in the private_key_manager. This simplifies ownership in the registry: otherwise we have to be pretty careful when people switch out keymanagers to ensure that things match together. PiperOrigin-RevId: 256664699
-
przydatek authored
PiperOrigin-RevId: 256643748
-
- Jul 04, 2019
-
-
Tink Team authored
PiperOrigin-RevId: 256491920
-
- Jul 03, 2019
-
-
tholenst authored
PiperOrigin-RevId: 256358888
-
tholenst authored
Furthermore, add a class PrivateKeyManagerImpl which will, internally, convert an internal public key manager and an internal private key manager to the corresponding private key manager. As usual, I recommend starting to read the test to see how things work. PiperOrigin-RevId: 256344393
-
- Jul 02, 2019
- Jul 01, 2019
-
-
przydatek authored
PiperOrigin-RevId: 255917787
-
- Jun 28, 2019
- Jun 27, 2019
-
-
przydatek authored
PiperOrigin-RevId: 255374294
-
candrian authored
Set omit_zlib=True to fix issue with io_bazel_rules_closure: no such target '@io_bazel_rules_closure//:third_party/zlib.BUILD' Upgrade io_bazel_rules_go to latest stable v0.18.6. Include .inc files in the tink_headers archive. This is needed by the //examples/helloworld/cc:non_bazel_build_test. PiperOrigin-RevId: 255372936
-
- Jun 26, 2019
-
-
Tink Team authored
PiperOrigin-RevId: 255194760
-
tholenst authored
Allow adding InternalPrivateKeyManagers together with their corresponding public key managers to the registry. We require public key manager at the same time because we need to get the key type. Doing this also has an advantage to the programmer: the compiler ensures that the public key types of the two given objects match, so I actually prefer this interface. PiperOrigin-RevId: 255166289
-
przydatek authored
-
przydatek authored
PiperOrigin-RevId: 255137607
-
- Jun 25, 2019
-
-
thaidn authored
PiperOrigin-RevId: 254977325
-
Yunchi Luo authored
-
candrian authored
PiperOrigin-RevId: 254955370
-
candrian authored
PiperOrigin-RevId: 254950816
-