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
https://evil32.com/ explains why we should reduce the use of 32-bit key IDs.
git-crypt writes commit messages with short key IDs:
// given a key fingerprint, return the last 8 nibbles std::string gpg_shorten_fingerprint (const std::string& fingerprint) { return fingerprint.size() == 40 ? fingerprint.substr(32) : fingerprint; }
Could we write the full fingerprints instead?
The text was updated successfully, but these errors were encountered:
08dbdcf
Good idea.
To be clear, git-crypt already uses exclusively full fingerprints internally. The commit message was the only place short IDs were being used.
Sorry, something went wrong.
No branches or pull requests
https://evil32.com/ explains why we should reduce the use of 32-bit key IDs.
git-crypt writes commit messages with short key IDs:
Could we write the full fingerprints instead?
The text was updated successfully, but these errors were encountered: