Make the key managers public, but restrict visibility of the constructors. Then, add a static function which registers them.

PiperOrigin-RevId: 269516892

PiperOrigin-RevId: 269020713

PiperOrigin-RevId: 268985498

PiperOrigin-RevId: 268913423

PiperOrigin-RevId: 268894131

Added InputStreamAdapter, which wraps an InputStream and adapts it for use in Python.

PiperOrigin-RevId: 268892335

PiperOrigin-RevId: 268878384

PiperOrigin-RevId: 268870105

PiperOrigin-RevId: 268743498

PiperOrigin-RevId: 268679436

PiperOrigin-RevId: 268678837

The target is still build visibility restricted, and hence should not be used by anyone.

PiperOrigin-RevId: 268668096

PiperOrigin-RevId: 268666385

This will be used to test the NewCcEncryptingStream wrapper function.

PiperOrigin-RevId: 268636936

PiperOrigin-RevId: 268436776

PiperOrigin-RevId: 268279920

PiperOrigin-RevId: 268270925

This isn't needed anymore, all key managers have been migrated to KeyTypeManagers.

PiperOrigin-RevId: 268229301

PiperOrigin-RevId: 268215250

PiperOrigin-RevId: 268196433

PiperOrigin-RevId: 268180258

PiperOrigin-RevId: 268168548

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

PiperOrigin-RevId: 268167203

PiperOrigin-RevId: 268166210

PiperOrigin-RevId: 267600331

PiperOrigin-RevId: 267595230
Change-Id: I3d960c326c913aa9f39cd92753a4c48bcfcea023

PiperOrigin-RevId: 267588997

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

Previously it was just a repeat of the test above.

PiperOrigin-RevId: 267583620

Change-Id: I3d960c326c913aa9f39cd92753a4c48bcfcea023

Migrate the tests for the EciesAeadHkdfPrivateKeyManager and add some tests for the corresponding public key manager.

PiperOrigin-RevId: 267579948

PiperOrigin-RevId: 267578883

PiperOrigin-RevId: 267572487

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