These versions are known to work well with each other.

PiperOrigin-RevId: 190175841
GitOrigin-RevId: 93684984c4f26263c658c3bf47a578b17123dcfd

PiperOrigin-RevId: 190145488
GitOrigin-RevId: c7fa32c67bfd64cb0ab0d5aebe41ba31102cd4f4

PiperOrigin-RevId: 190145333
GitOrigin-RevId: c19eff90e84224eed7e0338cd86868aa59c58e14

PiperOrigin-RevId: 190137127
GitOrigin-RevId: cecaa3b03ef39d8d48b5d64c16826ca1bb9b3a6c

Removing XChaCha20 and XSalsa20 because the former is too new and the latter is unlikely to be useful.

PiperOrigin-RevId: 190090084
GitOrigin-RevId: f25d42fd99e1bc7c4aaeb3cdeae90ca06ae21a43

Instead of reading key templates from disk, Tinkey now accepts key templates whose name is declared in Tink.

To create a keyset containing an AES128_GCM key, run

tinkey create-keyset --key-template AES128_GCM

Also removing the CreateKeyTemplate command and adding ListKeyTemplates.

PiperOrigin-RevId: 190088937
GitOrigin-RevId: 199694ecd4af61e512ea86249e5f5c9ba6684411

There are some format changes:
- The field notes in the header is now a dictionary.
- Test vectors have a new field flags, that should document the
  test vectors better. Additionally it can be used to change
  tests easier (e.g. a test can define if it cares about signature
  malleability or not).
- There are more special cases (e.g. implementations for brainpool curves
  can use the group isomorphisms defined in the standard).

Bug fixes:
- Some ECDH test vectors were missing a shared value.
- Some ECDH test vectors where the public key has modifications in unused
  parameters are now acceptable, as long as the change does not modify the
  shared secret.

PiperOrigin-RevId: 189929126
GitOrigin-RevId: b3e2b1caee4ba33c3dc4fcc223402527479e7140

PiperOrigin-RevId: 189588058
GitOrigin-RevId: 6d4389461fe9c341236eb2e8f3a7b87b8daf1d8b

PiperOrigin-RevId: 189384278
GitOrigin-RevId: ac7742b291f7da5af39739f03be43a41d554e5aa

PiperOrigin-RevId: 189379168
GitOrigin-RevId: 2524f3b25fbaa08011b512a2730265435f48db37

This reverts commit e3fdeda0b53175cca97d0b99a2c3811f6bf90310.

This feature adds a lot of code, but it's unused and it's not very
flexible because it supports only one JSON format, but I found that users
might store their keys in many different formats (e.g., PEM, JWK, etc.).

Instead of using a single, universal reader that, by delegating to key
managers, can parse arbitrary key types, we should add a series of small
readers, each can parse a specific key type, only when there's a clear
demand for them.

Change-Id: I64171ab08ab3d90515227137ebc8bdce13d09032
PiperOrigin-RevId: 189351693
GitOrigin-RevId: 4663a01d8b0cce2e4ee736e8621070eb571e1ba5

More information: go/java-maxpermsize-lsc

Tested:
    tap_presubmit
    Some tests failed; test failures are believed to be unrelated to this CL
PiperOrigin-RevId: 189284097
GitOrigin-RevId: b3b190888f663eda9492087f23f9e716ec33dd8d

PiperOrigin-RevId: 188924105
GitOrigin-RevId: 8dd7b38c0319064bc7c15bcb5d4dabc20fa733d9

Apparently we forgot to include the Ed25519Constants class. Wonder if there's a test to make sure this won't happen again.

PiperOrigin-RevId: 188899185
GitOrigin-RevId: 7d9e8ab87479535cc2a9ad790f203b643c25685e

PiperOrigin-RevId: 188897046
GitOrigin-RevId: 3a11d6ae9f32a5be7883403d988b04d5d9265725

PiperOrigin-RevId: 188896063
GitOrigin-RevId: b22b69140fcbd623a84384680f8aa1085dceb9e2

PiperOrigin-RevId: 188894007
GitOrigin-RevId: 1becb954afa7968c1ee73c107a120f07d87a30c3

Copying all Wycheproof test vectors to testdata/wycheproof and adding a few C++ transformation rules.

This is to prepare for cr/188575891.

PiperOrigin-RevId: 188892942
GitOrigin-RevId: 136568e214b16060e5e9750800533e50ed6eebe4

PiperOrigin-RevId: 188804612
GitOrigin-RevId: f74c008ce89de81d4aaa167b653e3043a6e19375

GitOrigin-RevId: 48a60f8a0fe15972da91802eec0b622925424024

GitOrigin-RevId: e71672b99e3072128702ac0fa4b26e258bcf2d75

PiperOrigin-RevId: 188493600
GitOrigin-RevId: 8ba4c6070e54951199c8d32150f1dd990875ce31

PiperOrigin-RevId: 188463467
GitOrigin-RevId: 0fd2ab773808de613c52e8143092ced7de7b5b26

CL 187175172 did add test vectors sorted by hash function and EC group.
This allows to limit the tests to the parameters supported by tink.

PiperOrigin-RevId: 188457817
GitOrigin-RevId: d51c93c849ff67253f8ae98bdb1d6ce8d829d683

PiperOrigin-RevId: 188447637
GitOrigin-RevId: 81c40d3546f63ffc8e996da0b44e1141ab3daba9

PiperOrigin-RevId: 188377796
GitOrigin-RevId: 673bd60bff3312c7d9911a36a9438ba3bb4a9240

PiperOrigin-RevId: 187930665
Change-Id: I140a9e3de957540cd0c6b40cc6a0c93dd0123575
GitOrigin-RevId: 39ca3a385405482e7c942728584e6c1c057aa9d4

Next I'll add some test to detect these errors early.

Also using rules_go 0.10.1 instead of master.

Change-Id: Ib79cd5c1ff7a6bb65cf588ee705183746c2cb417
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: b4ebcfbb4c99b01f21c330d1099ca230e4d4a46f

This makes migrating changes between GitHub and GoB easier.

The copybara script is being moved to Piper, and nobody is actually
using the other script.

Change-Id: I876e0ff90995e7d49fa97d57b86aee5d2e66b14a
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: e8463a41307fa0e81a8334cad4708dcc5316ed80

This is neater than x.y.z-SNAPSHOT because we don't have to update
the POM files when we release new snapshots which are always built
from HEAD of the master branch.

Change-Id: I07ded75e3e837b03db077787791599291ca6d478
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 95e2fc58566c73d633eb180191b63b868d1c6804

We no longer need to maintain Maven as a separate build and test system.
This would save us a lot of time, as Maven is not exactly nice to deal
with.

This also allows us to simplify the poms, especially the dependencies.
For example, to use Tink for Android users no longer have to set
$ANDROID_HOME.

Change-Id: I925b37409f8ed5e32f228d8de0f0845ea38bc427
ORIGINAL_AUTHOR=Google Engineers <noreply@google.com>
GitOrigin-RevId: 49470c492c6bc1d28960c243b671208863ccdf6b

Change-Id: I5b7e32a11a40ef1bb6236cc0a5c1b7f030f201e1
ORIGINAL_AUTHOR=Google Engineers <noreply@google.com>
GitOrigin-RevId: 1dc2f9b232006e087d30052fc98df76baf604d21

ORIGINAL_AUTHOR=Daniel Bleichenbacher <bleichen@google.com>

Change-Id: I26d2947c2b577932361c4c13ebf9e78adc6cab48
ORIGINAL_AUTHOR=Google Engineers <noreply@google.com>
GitOrigin-RevId: 33a309200923878e748799f59fb97d157b8897fa

This allows to use BUILD for Blaze.

Change-Id: I6fa84543b8ec927b0bdf5641f698b00d9c4de416
ORIGINAL_AUTHOR=Google Engineers <noreply@google.com>
GitOrigin-RevId: c049652c44d7e575d04169caf19d85b0d5371181

* Some cleanup

* Better error message for wycheproof file missing

Change-Id: I4f376ccef931346273539ba187747ca9ebf59d1c
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 7635e07b9dc9aa16534d67a10052da1b453e3fd0

Change-Id: I383c81354217e53dea318b0afb47b66db3e3659b
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 2fda3f2beb4d7763a36db641d47b69edc13b307e

Change-Id: Ifa509daa77d8994663dd3c3faca7ef6126ed8971
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 72ffad31af12c4bb50a555a52e6192fdf90c661e

Change-Id: Ifc233df77a9ca6c5f4a4cd39b4438fa2884bc9e7
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 74093277f729278619c47f765dcf56dd85580350

It is Go best practice to include generated pb.go files in repositories
so that a pure go implementation and tool chain can use the proto
libraries without special knowledge of protobuf.

The files are generated using the following command line from the root
folder of tink:

protoc -I=. --go_out=$GOPATH/src proto/tink.go
protoc -I=. --go_out=$GOPATH/src proto/ecdsa.go

and copy the generated file in
$GOPATH/src/github.com/google/tink/proto/tink_proto/tink.pb.go to
proto/tink_proto/.

With these files, go get github.com/google/tink/go/aead should download
and install the aead package.

Change-Id: I3021fb72951365b7bfb4a3086b1f351d7e88fa60
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 111162b28e94c09740a2ef524859a5f46fb8c70b