You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
Is it possible to implement a verification system that garantees that the pgp-signatures (*.asc files) are still correct and that the pgp-signer is still the same?
The current implementation of gradle-witness verifies that the checksum of the lib is correct.
As a developer every time i whish to use a new lib version i have to update the checksum, too.
With the pinned-pgp-signer verification i can declare trust in the signer. there is no need to update the signature in the gralde file when there are version updates. update is only neccessary if the pgp-signer changes
The text was updated successfully, but these errors were encountered:
Is it possible to implement a verification system that garantees that the pgp-signatures (*.asc files) are still correct and that the pgp-signer is still the same?
The current implementation of gradle-witness verifies that the checksum of the lib is correct.
As a developer every time i whish to use a new lib version i have to update the checksum, too.
With the pinned-pgp-signer verification i can declare trust in the signer. there is no need to update the signature in the gralde file when there are version updates. update is only neccessary if the pgp-signer changes
The text was updated successfully, but these errors were encountered: