Automated: Migrate fuchsia/third_party/tink from gsutil to gcloud storage This CL is part of the on going effort to migrate from the legacy "gsutil" tool to the new and improved "gcloud storage" command-line interface. "gcloud storage" is the recommended and modern tool for interacting with Google Cloud Storage, offering better performance, unified authentication, and a more consistent command structure with other "gcloud" components. 🚀 ⚠️ Action Required: Please Review and Test Carefully: While we have based the automation on the migration guide, every use case is unique. "IT IS CRUCIAL that you THOROUGHLY TEST these changes in environments appropriate to your use-case BEFORE MERGING." Be aware of potential differences between "gsutil" and `gcloud storage` that could impact your workflows. For instance, the structure of command output may have changed, requiring updates to any scripts that parse it. Similarly, command behavior can differ subtly; the "gcloud storage rsync" command has a different file deletion logic than "gsutil rsync", which could lead to unintended file deletions. Our migration guides can help guide you through a list of mappings and some notable differences between the two tools. Standard presubmit tests are run as part of this CL's workflow. "If you need to target an ADDITIONAL TEST WORKFLOW or REQUIRE ASSISTANCE WITH TESTING, please let us know." Please verify that all your Cloud Storage operations continue to work as expected to avoid any potential disruptions in production. Automation Details: This change was GENERATED AUTOMATICALLY by an agent that targets users of "gsutil". The transformations applied are based on the gsutil to gcloud storage migration guide - http://go/gsutil-gcloud-storage-migration-guide, external guide - https://docs.cloud.google.com/storage/docs/gsutil-transition-to-gcloud. Support and Collaboration: The "GCS CLI" team is here to help! If you encounter any issues, have a complex use case that this automated change doesn't cover, or face any other blockers, please don't hesitate to reach out. We are happy to work with you to test and adjust these changes as needed. Contact: gcs-cli-hyd@google.com We appreciate your partnership in this important migration effort! BUG: b:486536908 Change-Id: Ie776693a039bd1077d8773cbf4c4fb8b23bee563 Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/tink/+/1590170 Commit-Queue: Steve Fung <stevefung@google.com> Reviewed-by: Steve Fung <stevefung@google.com>
NOTE: Tink moved to github.com/tink-crypto and this repo is no longer active!
As planned, we have split Tink into multiple GitHub repositories that are hosted at github.com/tink-crypto. As a consequence, we made this repository read-only and it is not going to be maintained moving forward.
A multi-language, cross-platform library that provides cryptographic APIs that are secure, easy to use correctly, and hard(er) to misuse. See also: https://developers.google.com/tink.
Using crypto in your application shouldn't have to feel like juggling chainsaws in the dark. Tink is a crypto library written by a group of cryptographers and security engineers at Google. It was born out of our extensive experience working with Google's product teams, fixing weaknesses in implementations, and providing simple APIs that can be used safely without needing a crypto background.
Tink provides secure APIs that are easy to use correctly and hard(er) to misuse. It reduces common crypto pitfalls with user-centered design, careful implementation and code reviews, and extensive testing. At Google, Tink is one of the standard crypto libraries, and has been deployed in hundreds of products and systems.
To get a quick overview of Tink design please take a look at slides from a talk about Tink presented at Real World Crypto 2019.
Java/Android, C++, Obj-C, Go, and Python are field tested and ready for production. The latest version is 1.7.0, released on 2022-08-09.
Javascript/Typescript is in an alpha state and should only be used for testing. Please see the intent to remove statement here.
Ubuntu | macOS |
|---|---|
 |  |
Documentation for the project is located at https://developers.google.com/tink. Currently, it details a variety of common usage scenarios and covers the Java and Python implementations. The site will be populated with more content over time.
Alternatively, you can look at all of the examples which demonstrate performing simple tasks using Tink in a variety of languages.
pip3 install tink
go get github.com/google/tink/go/...
<dependency> <groupId>com.google.crypto.tink</groupId> <artifactId>tink</artifactId> <version>1.7.0</version> </dependency>
dependencies {
implementation 'com.google.crypto.tink:tink-android:1.7.0'
}
cd /path/to/your/Xcode project/ pod init pod 'Tink', '1.7.0' pod install
Out of the box Tink supports a wide range of languages, but it still doesn‘t support every language. Fortunately, some users like Tink so much that they’ve ported it to their favorite languages! Below you can find notable ports.
WARNING While we usually review these ports, until further notice, we do not maintain them and have no plan to support them in the foreseeable future.
If you want to contribute, please read CONTRIBUTING and send us pull requests. You can also report bugs or file feature requests.
If you'd like to talk to the developers or get notified about major product updates, you may want to subscribe to our mailing list.
Tink is maintained by (A-Z):
Alumni: