NekoX
                                
                                
                                
                                    NekoX copied to clipboard
                            
                            
                            
                        GPG EC pubkey sharing
Describe the bug I am trying to share my public GPG key in telegram chat. It works fine on locally-generated RSA key, but if I use my imported EC key, NekoX tries to send the message with its contents, however the message itself is not sent and keeps hanging with red exclamation mark symbol and with "retry" button, which obviously does not help... The key is stripped and is contained on Nitrokey device, however its' public part is received from keyserver and is available for any app.
To Reproduce Steps to reproduce the behavior:
- Import EC key in OpenKeychain (Signature: NISTp521, Encryption: Brainpoolp512, Auth: NISTp521)
 - Enable NekoX OpenKeychain integration
 - Go to any chat and share your gpg pubkey
 - The message is not sent
 
Note: Maybe the message is too long? In fact I have the key and six subkeys, three of which were revoked (to work around OKC issues) Maybe we should share pubkeys as files?
Logcat Settings - click version - "Enable Log", then click "Send Logs" to @NekoXChat or just upload at issue.
Expected behavior Any pubkey gets sent successfully
Smartphone (please complete the following information):
- Device: Samsung Galaxy Note 10+ (SM-N975F)
 - OS: LineageOS 19.1 (Android 12)
 - Version Nekogram X 8.7.4 (F-Droid)/OpenKeychain 5.7.5 (F-Droid)
 
Additional context Is there any documentation on GPG integration? I'm unable to find anything regarding encryption (only signature) - only three issues in one of which @MuratovAS stated that he implemented the encryption feature. Was it merged? Sounds like a killer feature to me =)
Greetings @Unb0rn
The encryption function violates TOS, the probability of adding it is minimal. As far as I know all PR and issues are closed.
If you really need this feature. You can merge yourself.
The bug you describe occurs because your key exceeds the maximum message length.
P.S. If you really need this function, I advise you to use oversec.
@MuratovAS Thank you! I think manual merge seems to be a better solution - looks like oversec is dead and unmaintained anymore. It has compatibility issues with Android 12. I think will keep this one open for a while - sharing pubkey as a file feels like a better solution (no length limits at least)