Updated Google Summer of Code 2015 (markdown)
parent
f6fdb7abcd
commit
7c15e591f7
|
@ -113,9 +113,18 @@ student will get yubikey.
|
||||||
* new lockpattern lib
|
* new lockpattern lib
|
||||||
* etc
|
* etc
|
||||||
|
|
||||||
## Deletion operations
|
## Key Deletion UX/Revocation
|
||||||
* really delete? -> revocation?
|
**Brief explanation:** When deleting a key the user should be asked to revoke the key if it is a secret one instead of just deleting it. Deleting a secret key should be considered an expert option, the average user should not do. Furthermore, revocation certificates should be supported in general. As part of the key generation process and for revoking a key at a later point in time.
|
||||||
* revocation certificates
|
|
||||||
|
**Expected results:** Better UX when deleting keys/Support for revocation certificates
|
||||||
|
|
||||||
|
**Knowledge Prerequisite:** Java programming
|
||||||
|
|
||||||
|
**Skill level:** medium
|
||||||
|
|
||||||
|
**Mentor:** Dominik Schürmann
|
||||||
|
|
||||||
|
**Contact:** [Mailinglist](http://groups.google.com/d/forum/openpgp-keychain-dev) or over XMPP (Jabber-ID: dominik@dominikschuermann.de)
|
||||||
|
|
||||||
## File Decryption Screen
|
## File Decryption Screen
|
||||||
**Brief explanation:** Currently the file decryption screen in OpenKeychain only allows to decrypt one file at a time and only allows saving of decrypted files into the filesystem. While this is okay for simple scenarios. The decryption process could result in many files being decrypted. Either when multiple files are shared together using Android's [ACTION_SEND_MULTIPLE](http://developer.android.com/training/sharing/receive.html#handling-content) or when the OpenPGP data structure contains many parts. Thus, the screen should be extended for multiple files. A list of files should be displayed like done in the encryption screen that with the options save/open per file item. To get the right content type and decrypt the filename the new internal DECRYPT_METADATA functionality of OpenKeychain should be used. The real payload should be decrypted when save/open is clicked. Furthermore the recipient's key user id should be displayed inside the item.
|
**Brief explanation:** Currently the file decryption screen in OpenKeychain only allows to decrypt one file at a time and only allows saving of decrypted files into the filesystem. While this is okay for simple scenarios. The decryption process could result in many files being decrypted. Either when multiple files are shared together using Android's [ACTION_SEND_MULTIPLE](http://developer.android.com/training/sharing/receive.html#handling-content) or when the OpenPGP data structure contains many parts. Thus, the screen should be extended for multiple files. A list of files should be displayed like done in the encryption screen that with the options save/open per file item. To get the right content type and decrypt the filename the new internal DECRYPT_METADATA functionality of OpenKeychain should be used. The real payload should be decrypted when save/open is clicked. Furthermore the recipient's key user id should be displayed inside the item.
|
||||||
|
@ -123,7 +132,7 @@ A related problem are [hidden recipients](https://github.com/open-keychain/open-
|
||||||
The "delete after decryption" functionality needs to be re-designed for this task.
|
The "delete after decryption" functionality needs to be re-designed for this task.
|
||||||
Also "detached signatures" should be supported by the new decryption screens. An internal method has already been done during the work on PGP/MIME. This can be used, but needs a carefully designed UI.
|
Also "detached signatures" should be supported by the new decryption screens. An internal method has already been done during the work on PGP/MIME. This can be used, but needs a carefully designed UI.
|
||||||
|
|
||||||
**Expected results:** Backup/Restore functionality.
|
**Expected results:** Nice decryption screen
|
||||||
|
|
||||||
**Knowledge Prerequisite:** Java programming
|
**Knowledge Prerequisite:** Java programming
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue