Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I just saw that GnuPG 2.1.15 stores its secret keys in a different location:
The old GnuPG (1.x, maybe even including 2.0.x) stored the secret keys in:
When upgrading from GnuPG 1.x to 2.x, the secret keys are automatically migrated and the file
Btw. it is possible as a workaround, though, to delete the file
Also, when GnuPG 2.x creates a new secret key pair, the
Subshare should be extended to detect whether the GnuPG 2.x is used and should then read the secret keys from the new sub-directory! Also when creating new key pairs, it should write them into the new sub-directory.
But Subshare should still be compatible with GnuPG 1.x, too!!! Thus, if GnuPG 2.x is not used, Subshare should work exactly like it's doing now.
Maybe, subshare should even check, if the old
According to http://stackoverflow.com/questions/34212230/using-bouncycastle-with-gnupg-2-1s-pubring-kbx-file the public keys are stored in a different file format, too, by default. However, GnuPG 2.1 continues to use the old
I asked on the dev-crypto mailing-list and the BC team said that the new file formats are on their to-do list. But they don't know, yet, when they are going to be supported. Definitely, they are not yet supported, right now.
This issue thus needs to be postponed.
As a temporary workaround, I added the deletion of the file
This is included in subshare 0.10.0. A proper solution is coming later, when a new BouncyCastle supports the new GPG 2.1 file formats.