PiperOrigin-RevId: 257174178

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

PiperOrigin-RevId: 256994544

PiperOrigin-RevId: 256984303

when one gets the public key.

This was somehow not done previously.

PiperOrigin-RevId: 256951691

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

PiperOrigin-RevId: 256940676

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

PiperOrigin-RevId: 256643748

PiperOrigin-RevId: 256491920

PiperOrigin-RevId: 256358888

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

PiperOrigin-RevId: 256197192

PiperOrigin-RevId: 256137427

PiperOrigin-RevId: 255917787

PiperOrigin-RevId: 255588927

PiperOrigin-RevId: 255586012

PiperOrigin-RevId: 255577505

PiperOrigin-RevId: 255374294

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

PiperOrigin-RevId: 255194760

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

PiperOrigin-RevId: 255137607

PiperOrigin-RevId: 254977325

PiperOrigin-RevId: 254955370

PiperOrigin-RevId: 254950816

PiperOrigin-RevId: 254925043

I need to set the variables used in run_tests_cmake.sh manually from outside; I think this is the better way. However, I'm not sure I should do it somehow differently -- please check if this is the way this test should be run.

PiperOrigin-RevId: 254924611

PiperOrigin-RevId: 254916066

PiperOrigin-RevId: 254873900

PiperOrigin-RevId: 254765336

PiperOrigin-RevId: 254732829

PiperOrigin-RevId: 254725725

PiperOrigin-RevId: 254709236

Create a new kokoro config which runs the tests only under CMake; remove the tests from the other config.

PiperOrigin-RevId: 254697776

PiperOrigin-RevId: 254484768

PiperOrigin-RevId: 254477492

PiperOrigin-RevId: 254376525