johnyb / ox_pgp_mail Goto Github PK

A short list of tasks that would need to be done:

• check for key existance (not possible)
• start decryption if private key is in keyring

TODO:

• add new editor implementation
• send PR upstream to refactor editor interface
• check for availability of public keys
• correctly handle missing public keys (fail)
• try to import missing public keys (moved to a new issue)
• provide plain MIME data from MailModel instance
• overwrite "send" call, because we need to send plain MIME data
• sketch out improved API for sending (send upstream)

Provide a basic API to manage keys for different sources. One should be mailvelope, others might be Guard or keybase.io.

• package for Debian-like distros
• package for RPM based distros

• - add a settings pane for mailvelope
• - render mailvelope settings iframe

Use mailvelope API to backup private keys

• backup to OX Guard
• restore from OX Guard

When composing a new mail, some recipients might not have public keys in mailvelope. There should be some support to get those keys into the keyring.

• show state within tokenfields (like OX Guard does)
• provide minimal help about what is wrong and how to fix the problem
• import from Guard (may be defer, if it's too hard)
• import file
• import plain text

At the moment, an entry in the Editor section of the "Options" dropdown is used to activate mailvelope editor. To be consistent with OX Guard, use a lock icon in the headers instead.

As a new user without having Mailvelope set up
in order to get the system up and running
I want to be guided through the setup process.

• start wizard on keyring creation
• wizard step: install mailvelope plugin
• wizard step: generate key
• wizard step: backup key (optional) (no working backend available)