-
Notifications
You must be signed in to change notification settings - Fork 529
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
[Security] git verify-commit everywhere #2686
Comments
YES !!! |
Note that you can run Also be mindful of downgrade attacks (an attacker could send a valid old signed version with known vulnerability so that he can then exploit it). |
yes, but some keys are not shared on the keyservers unfortunately. I find it best when people share it on their own website and then can be double checked in person, on a keyserver and maybe having some verified signatures too from other known entities ("circle of trust"). |
So far all keys I use are on keyserver (Ubuntu), if there are any missing it may be nicer to ask people to share them. |
keys are downloaded to pgp_keys.asc imported only from that file and checked for fingerprint exit status is used to verify signature discussed in: raspiblitz#2683 raspiblitz#2686
PR merged for final testing |
Works so far good with RCs .. closing foir release. |
Introducing a script d514402 to verify the checked out git commits with the BTCpay update: #2683
All scripts installing services built from the source code can have a header like:
and can run:
to reduce trust in the download source.
Failing to verify the PGP signature on the checked commit breaks the installation.
Can implement this on all services as we go on applying the pinned updates.
The text was updated successfully, but these errors were encountered: