We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This helps with the bootstrapping problem.
Docs for git tags: https://help.github.com/articles/signing-tags-using-gpg/ Example for PIP release: https://github.com/ypid/fdeunlock/blob/bb1728e32657a0824410cacc82371fdc4c31d253/Makefile#L146-L151 Related to: #182 (comment)
Examples:
The text was updated successfully, but these errors were encountered:
Closing this to keep the discussion in one issue.
Sorry, something went wrong.
Quoted from #182 (comment):
#184 doesn't help Debian unless they actually check the signature, and nothing tells me they do.
Then let me do that: https://wiki.debian.org/debian/watch#Cryptographic_signature_verification
It's also only one of the distribution channels
Other distros have similar models. But they all depend on the abilities of the upstream project.
and unfortunately people will just add any old gpg key to the apt or yum/dnf keyring that they find these days.
Security minded people will never do that.
This might still be a valid issue.
No branches or pull requests
This helps with the bootstrapping problem.
Docs for git tags: https://help.github.com/articles/signing-tags-using-gpg/
Example for PIP release: https://github.com/ypid/fdeunlock/blob/bb1728e32657a0824410cacc82371fdc4c31d253/Makefile#L146-L151
Related to: #182 (comment)
Examples:
The text was updated successfully, but these errors were encountered: