Destroyed Known Issues (markdown)
parent
117e239961
commit
75a93f6208
|
@ -1,19 +0,0 @@
|
|||
### Importing secret key fails
|
||||
Before posting a new bug report, please check if you are using gpg prior to 2.1.0 and changed the expiry date before exporting the secret key.
|
||||
|
||||
Changing the expiry date of a key in gpg prior to version 2.1.0 breaks the secret key in a way which emerges only on export. It's not a problem with OpenKeychain, we correctly reject the key because its self-certificates are either invalid, or have wrong flags.
|
||||
|
||||
This issue has been reported before (#996, #1026), and can be assumed to affect a large number of users. The bug in gpg has been fixed in gpg 2.1.0, but that version is as of now [only deployed in debian experimental](https://packages.debian.org/search?keywords=gnupg2), not even sid. Another [bug report]
|
||||
(https://bugs.g10code.com/gnupg/issue1817) has been opened by jas just today to backport the fix, so I hope this gets fixed soonish.
|
||||
|
||||
* https://github.com/open-keychain/open-keychain/issues/996
|
||||
* https://github.com/open-keychain/open-keychain/issues/1003
|
||||
* https://github.com/open-keychain/open-keychain/issues/1026
|
||||
|
||||
### A wrong primary user id is shown when searching on a Keyserver
|
||||
Unfortunately, this is a bug in the SKS Keyserver software. Its machine-readable output returns the user ids in an arbitrary order. Read the [related bug report](https://bitbucket.org/skskeyserver/sks-keyserver/issue/28/primary-uid-in-machine-readable-index) for more information.
|
||||
|
||||
### Not working with AOSP Mail
|
||||
For now, OpenKeychain will not support AOSP Mail.
|
||||
|
||||
* https://github.com/open-keychain/open-keychain/issues/290
|
Loading…
Reference in New Issue