Git doesn't see gpg key as secret, even though it is, how do I fix it?
来源： https://stackoverflow.com/questions/55111685/git-doesnt-see-gpg-key-as-secret-even-though-it-is-how-do-i-fix-it
gpg-signature
Git doesn't see gpg key as secret, even though it is, how do I fix it?
来源： https://stackoverflow.com/questions/55111685/git-doesnt-see-gpg-key-as-secret-even-though-it-is-how-do-i-fix-it
Verification of PGP signature using BouncyCastle
问题 I've generated a PGP Signature: -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBBABCAAGBQJYnkPxAAoJEBFjzYGyXBOsXRoH/3O4bwKK45aUN+m0N4jsZ+n5 W8R/aGti/llvJ62tHBCO5BIp/pp+b1Gdv99xtnJXHu/f0TqPYj+fwq4vfaorNTtA Vtq8MaMesw1OWZEfu/lyjNOwdg81FUlYkw0Bjo3H/MxWjWYUiHmJo+OGriyf5dv/ 433ZqitZMxLHCfZsuoU5teZ0BPUSoNjF6hOFK3ZI7QXsgYUyohzW2goy9bDVCKRq e73CHpnMKCrnDc+/4+sK349bD/cZp6/c0T8b7cBCeBGGilPD6ovJUQE5vhGTKnJM lgyxhA87tw9wqFwpZXDr0nzOP+MFfE9WRGecVYZ9G+LP/biefSe5iWRaPIcZIi0= =qUHb -----END PGP
Verification of PGP signature using BouncyCastle
问题 I've generated a PGP Signature: -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBBABCAAGBQJYnkPxAAoJEBFjzYGyXBOsXRoH/3O4bwKK45aUN+m0N4jsZ+n5 W8R/aGti/llvJ62tHBCO5BIp/pp+b1Gdv99xtnJXHu/f0TqPYj+fwq4vfaorNTtA Vtq8MaMesw1OWZEfu/lyjNOwdg81FUlYkw0Bjo3H/MxWjWYUiHmJo+OGriyf5dv/ 433ZqitZMxLHCfZsuoU5teZ0BPUSoNjF6hOFK3ZI7QXsgYUyohzW2goy9bDVCKRq e73CHpnMKCrnDc+/4+sK349bD/cZp6/c0T8b7cBCeBGGilPD6ovJUQE5vhGTKnJM lgyxhA87tw9wqFwpZXDr0nzOP+MFfE9WRGecVYZ9G+LP/biefSe5iWRaPIcZIi0= =qUHb -----END PGP
Intellij IDEA signing GIT commits with GPG
问题 GPG signing of GIT commits works in terminal but not in Intellij Idea. gpg failed to sign the data fatal: failed to write commit object 回答1: If you have working GPG signing of your GIT commits in terminal but not in Intellij Idea you can use pinentry-mac . Don't forget to update your gpg.conf and gpg-agent.conf files as well. brew install pinentry-mac echo "no-tty" >> ~/.gnupg/gpg.conf echo $(which pinentry-mac) >> ~/.gnupg/gpg-agent.conf More information here: https://nathanielhoag.com/blog
Android Studio gradle bintray upload failed: Could not sign version
问题 After running ./gradlew bintrayUpload I am getting the following error. :my-library:bintrayUpload FAILED FAILURE: Build failed with an exception. What went wrong: Execution failed for task ':my-library:bintrayUpload'. Could not sign version '0.8.1': HTTP/1.1 400 Bad Request [message:Private key is required, please supply it by using a JSON body or alternatively you can stored in your Bintray profile] Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option
Why does git sign with GPG keys rather than using SSH keys?
问题 What are the differences between SSH and GPG asymmetric keys and why does git support signing with GPG rather than using the SSH agent? 回答1: The very first notion of signing anything in Git was referenced in commit ec4465a, Git v0.99, Apr. 2005 (pretty much from the very beginning) /** * A signature file has a very simple fixed format: three lines * of "object <sha1>" + "type <typename>" + "tag <tagname>", * followed by some free-form signature that git itself doesn't * care about, but that
GPG error when using 'stack upload'
问题 When I run stack upload I get an error: Environment variable GPG_TTY is not set (see man gpg-agent) Unable to find gpg2 or gpg executable The upload appears to succeed, but the error concerns me. What are the consequences of this error? Is there a way to avoid to suppress it? 回答1: As per discussion in the comments the errors are due to stack trying to automatically GPG sign packages that are being uploaded as of version 1.1.0. To my understanding this is a stack-specific feature (with no
GPG error when using 'stack upload'
When I run stack upload I get an error: Environment variable GPG_TTY is not set (see man gpg-agent) Unable to find gpg2 or gpg executable The upload appears to succeed, but the error concerns me. What are the consequences of this error? Is there a way to avoid to suppress it? As per discussion in the comments the errors are due to stack trying to automatically GPG sign packages that are being uploaded as of version 1.1.0 . To my understanding this is a stack-specific feature (with no package signing built into cabal or hackage), and it can be disabled with --no-signature command line option to
gpg failed to sign the data fatal: failed to write commit object [Git 2.10.0]
I followed few articles over the pretty attributes on Git 2.10 release note. Going through which upgraded the git to 2.10.0 and made changes to global .gitconfig resulting as follows - [filter "lfs"] clean = git-lfs clean %f smudge = git-lfs smudge %f required = true [user] name = xyz email = abc.def@gmail.com signingkey = AAAAAAA [core] excludesfile = /Users/xyz/.gitignore_global editor = 'subl' --wait [difftool "sourcetree"] cmd = opendiff \"$LOCAL\" \"$REMOTE\" path = [mergetool "sourcetree"] cmd = /Applications/SourceTree.app/Contents/Resources/opendiff-w.sh \"$LOCAL\" \"$REMOTE\"