Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set Gradle verification to check the dependency have been compromised #1410

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Jaehwa-Noh
Copy link
Contributor

What I have done and why

Set Gradle verification.
From this documentation

Working with external dependencies and plugins published on third-party repositories puts your build at risk. In particular, you need to be aware of what binaries are brought in transitively and if they are legit. To mitigate the security risks and avoid integrating compromised dependencies in your project, Gradle supports dependency verification.

Gradle can check dependencies' checksum in build time, and verify that dependencies have been compromised.
I set Gradle option for just warning when checksum throw error.
If you want to make new verification-metadata.xml, run this gradle --write-verification-metadata sha256 check

How I'm testing it

Choose at least one:

  • Unit tests
  • UI tests
  • Screenshot tests
  • N/A (provide justification)

Change-Id: Ic61948e43b25d2133c05765a9d69362f8111be50
Change-Id: I0385ed412a52420e1679f9efcfaa66032e8dcec8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant