PiperOrigin-RevId: 265029049

PiperOrigin-RevId: 264828112

PiperOrigin-RevId: 264827426

PiperOrigin-RevId: 264813307

PiperOrigin-RevId: 264802865

PiperOrigin-RevId: 264690696

PiperOrigin-RevId: 264679745

PiperOrigin-RevId: 264610922

PiperOrigin-RevId: 264609510

This is done in order to facilitate multiple primitives. See cl/263297547 for an example.

We will migrate the tests to ues the KeyTypeManager interface directly in an upcoming cl (as the new interface is easier to test).

PiperOrigin-RevId: 264608819

PiperOrigin-RevId: 264608183

Perviously, the wrong code was compiled there.

PiperOrigin-RevId: 264595321

PiperOrigin-RevId: 264584665

PiperOrigin-RevId: 264581506

Migrate the key proto format for ChaCha20/Poly1305 and XChaCha20/Poly1305 from Empty to formats specific for these types in Java.

PiperOrigin-RevId: 264579991

PiperOrigin-RevId: 264576569

PiperOrigin-RevId: 264576360

With the new KeyTypeManager implementation, tests can be made simpler.

PiperOrigin-RevId: 264572956

Migrate the key proto format for ChaCha20/Poly1305 and XChaCha20/Poly1305 from Empty to formats specific for these types.

PiperOrigin-RevId: 264569912

The tests will be migrated in a follow up cl.

*NOTE* that I change how some of the things are done. In particular, previously:
  * The underlying HMac was generated by calling the registry.
  * The underlying HMac key was manually created, without going through the registry. The version was set wrongly (to the version of the AesCtrHmacAeadKeyManager instead of the HMacKeyManager).
  * The underlying HMac key was now validated in this key manager.
  * The underlying HMac format was not validated.

After this cl, I use the HMac KeyTypeManager to validate things; and I do that directly without going through the registry.

I think the proper way would be to have some kind of registry access, where this KeyManager can obtain the new HMacKey *Type* manager, and then do the proper things. But this is complicated :/ I think this here is the second best solution.

PiperOrigin-RevId: 264568255

PiperOrigin-RevId: 264564958

the return value to StatusOr<int64_t>, to allow richer error reporting.

PiperOrigin-RevId: 264455697

PiperOrigin-RevId: 264384749

PiperOrigin-RevId: 264382855

This uses KeyTypeManagers to implement the ECIES Key Managers; making the code slightly simpler.

The main simplification happens when we update the tests in a follow up cl.

PiperOrigin-RevId: 264382557

Newer ABSL breaks CMake build.

*** Original change description ***

Bumping up ABSL-version.

PiperOrigin-RevId: 264381021

PiperOrigin-RevId: 264374853

PiperOrigin-RevId: 264336131

PiperOrigin-RevId: 264334119

PiperOrigin-RevId: 264275386

PiperOrigin-RevId: 264116863

I will add this to Tink, including cross language tests and performance testing. I think we can remove Alpha then.

PiperOrigin-RevId: 264114752

More context in cl/263529237.

PiperOrigin-RevId: 264099137

PiperOrigin-RevId: 263753529

PiperOrigin-RevId: 263752000

PiperOrigin-RevId: 263751184

We will migrate the test in an upcoming cl.

PiperOrigin-RevId: 263749532

PiperOrigin-RevId: 263748450

PiperOrigin-RevId: 263722626

This function has the contract that it doesn't need to initialize the string when resizing. At the moment, the only implementation we have is the one which does the additional work of actually resizing the string.

PiperOrigin-RevId: 263559220