fix(deps): update dependency com.google.crypto.tink:tink-android to v1.18.0 #4897
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.17.0
->1.18.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
tink-crypto/tink-java (com.google.crypto.tink:tink-android)
v1.18.0
: Tink Java v1.18.0Tink is a multi-language, cross-platform library that provides simple and
misuse-proof APIs for common cryptographic tasks.
This is Tink Java 1.18.0
The complete list of changes since 1.17.0 can be found here.
Dropped support
Tink Android no longer supports API level 21 and 22. From Tink 1.18.0, the
minimum API level is 23.
Removed
Registry.wrap
. This API cannot have been used by users: thePrimitiveSet
needed for it was already moved to internal in Tink 1.13.0.New Features
Use Conscrypt's implementation of
Ed25519
when available.Improved performance of AES-GCM-SIV.
Tink now provides a flag
GlobalTinkFlags.validateKeysetsOnParsing()
. Ifset to true, Tink will run certain validations on a keyset before it creates
a
KeysetHandle
. We plan to flip the default of this flag to true in Tink2.0.
Bug fixes
AeadConfig.register()
now always registers AES-GCM-SIV. If it's notsupported by the registered JCE Providers, it will fail when the primitive
is created.
The Aead implementation returned by
com.google.crypto.tink.integration.android.AndroidKeystore.getAead()
created invalid ciphertexts on Android API version 28 and older when
the input was larger than 128kB. Now, it throws an exception instead.
JwtHmacKey
,LegacyKmsAeadKey
, andLegacyKmsEnvelopeAeadKey
are nowfinal. These cannot be properly subclassed as this would break
equalsKey
.Obscure behaviour changes
available. Previously, this used to work with some Configurations succeeding
and the primitive then failed when encrypt or decrypt was called.
Future work
To see what we're working towards, check our
project roadmap.
Getting started
To get started using Tink, see
the setup guide.
Maven:
Gradle:
Bazel:
Alternatively, one can build Tink from source, and include it with
http_archive
:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.