Kopete - PGP Plugin (GSoC 2015)
Nikos Chatzidakis <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kopete |
|---|---|
| Message-ID | <CAHnpvVdOSuGiAHLyV1bL3kfF9-_r781VtVWzhJ-sUUBVkipVWw@mail.gmail.com> |
Hello everybody, Below I attach the updated timeline for this year's GSoC project, where you can find detailed information about my current (and future) work. For the time being, there is a git repo which you can find here: http://nikhatzi.gr:9091/nikhatzi/kopete (latest code will be updated in about 2-3 days, as I study for my exams too). My project is also updated in the kde gsoc reports status page. Frequent e-mails will be sent from now on to this list to update everyone interested with the latest changes. Thank you for your time and the opportunity to work on this awesome project! Yours, Nikolaos Chatzidakis _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
gsoc_pgp.txt
(text/plain, 2.9 KB)
GSoC 2015 PGP Plugin Timeline (updated) By the time of writing this timeline, the backbone of the PGP plugin is ready. Some problems occurred though, that need to be resolved with the respective developers of the library used in the project (QCA). June 22-30: Add account menu in plugin so that the user can select different key for every account that he/she uses. The KCM module is ready and able to display a combo list to select a key for encrypting messages. All info combined will be store in the gnupg-keyring. July 1-12: Expand the PGP plugin to make it easy for the user to select a contacts public key. Corresponding menu will be added in kopetes right-click menu to simplify usage. The same time, the chat window will be configured to allow an encrypted session initiation, after contacting with the other person to verify that he has our public key selected. (There will be no public key validation for obvious reasons. Doing so via an unencrypted channel provides no protection at all) 13-19: Alpha version of PGP plugin. There will be a public call for help. Users will be able to try the new plugin, test it thoroughly and report any bugs found to be resolved. 20-26: The new PGP plugin uses the QCA Qt library for encrypting/decrypting messages, as well as storing the keys info in the gnupg-keyring. Current version in most GNU/Linux distributions is <2.1, which results to installing the QCA plugins as a separate package. Since version 2.1 (stable), QCA is bundled with all the plugins included, which means that the new plugin must take into account the version of QCA and respond respectively, so that it will be backwards compatible with older versions of the library. During this period there will be a contact with the QCA developers to clear things up on how to proceed. 27-31: After expanding the plugin to be backwards compatible there will be Beta version of the plugin with public call for help. Users with any QCA library version will be asked to try the new version to insure interoperability of the new plugin. Bugs will be fixed. August 1-9: Since in this years GSoC kopete is under heavy development, a fellow GSoCer is responsible for porting Kopete to latest KF5 libraries. Its a good idea to start porting the plugin to the new KF5 libraries and make it compatible with the new release of kopete. This way we can be sure that the new plugin wont create any problems with later version of Kopete and will last for a long time using latest technologies. 10-16: Heavy development with the help of R. Harish Navnit for kopete-kf5 specific issues. 17-24: Unit testing of final PGP release, bug fixing and documentation. Notes: During this timeline I omitted the evaluation periods, and didnt count them as dead time during GSoC, since the PGP plugin is an ongoing work and time-demanding to be left for some days on its own.