-
I wonder if anyone knows the answer to this one, related to GPG key generation. I'm integrating GPG signing of commits with JGit into our RCP app and testing with GPG keys. I have successfully created GPG keys using GnuGP on Linux and Mac but not on Windows. Using Windows GnuGP a The command I use is:
BouncyCastleGpgKeyLocator requires the Is this some new format not yet supported in BC/JGit or is something else going on? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
After a conversation with Grok I discovered that since GnuPG 2.4.1 GnuGP on Windows may default to using the In order to workaround this one can create an empty If this becomes the default format going forward I wonder if this will be supported in BC/JGit? Edit - see eclipse-egit/egit#12 |
Beta Was this translation helpful? Give feedback.
After a conversation with Grok I discovered that since GnuPG 2.4.1 GnuGP on Windows may default to using the
use-keyboxd
option, which relies on a SQLite-based backend (pubring.db
in~/.gnupg/public-keys.d/
) instead of creating apubring.kbx
file. See here and here.In order to workaround this one can create an empty
~/.gnupg
directory first or if a~/.gnupg/common.conf
file exists edit it so thatthe
use-keyboxd
entry is removed or commented out like#use-keyboxd
If this becomes the default format going forward I wonder if this will be supported in BC/JGit?
Edit - see eclipse-egit/egit#12