Difference between revisions of "Summer of Code 2015"

Jump to navigation Jump to search
2,626 bytes added ,  15:47, 19 February 2015
no edit summary
m
Line 44: Line 44:
* '''Mentor:''' Kevin Smith, Tobias Markmann
* '''Mentor:''' Kevin Smith, Tobias Markmann
* '''Contact Details:''' Chatroom at swift@rooms.swift.im
* '''Contact Details:''' Chatroom at swift@rooms.swift.im


=== Openfire Message Archive Management support ===
=== Openfire Message Archive Management support ===
Line 173: Line 172:
* '''Mentor:''' Simon Tennant
* '''Mentor:''' Simon Tennant
* '''Contact details:''' https://groups.google.com/forum/#!forum/buddycloud-dev
* '''Contact details:''' https://groups.google.com/forum/#!forum/buddycloud-dev
=== axolotl support for Conversations ===
* '''Software Project:''' Conversations
* '''Software URL:''' http://conversations.im
* '''Software VCS URL:''' https://github.com/siacs/Conversations
* '''Software Description:''' Conversations is an XMPP client for Android that features optimizations for the use in a mobile environment like message synchronization across devices and battery optimization techniques. Conversations tries to be accessible to an audience that has no prior experience with XMPP by eliminating a lot of configuration options and replacing them with sane defaults or automation.
* '''Brief explanation:''' Conversations already comes with a choice of end-to-end encryptions. Currently the user can decide between OTR and openPGP which unfortunately both have some downsides. With OTR enabled, for example, messages can no longer be synced across devices. The axolotl encryption protocol, which is currently used by the TextSecure client, can solve these problems as described  [https://blog.thijsalkema.de/me/blog//blog/2015/01/23/multi-end-to-multi-end-encryption/ here]. There is already a java library that implements [https://github.com/WhisperSystems/libaxolotl-android axolotl for Android].  Conversations itself comes with a lot of features that make an implementation easier like general crypto support (UI elements), message synchronization (carbon copies, message archive management) and PEP support (can be used to publish the keys)
* '''Expected results:''' Implement libaxolotl support in Conversations. Come up with a way to send axolotl encrypted messages in XMPP messages. Implement a mechanism to publish what axolotl calls PreKeys over PEP or another suitable mechanism and have others users fetch those keys. Make this work with carbon messages (=multiple receiving clients). Not part of GSOC but this proof of concept implementation will later be used to propose a XEP and allow other clients to use the same standard. Potential participants won't be expected to be part of this standardization process but they will definitely have the chance to.
* '''Knowledge Prerequisite:''' XMPP, Java, a bit of Android (you probably won't have too much contact with Android specifics because the UI work is already done for the most part), some awareness for crypto and security. You don't have to be a cryptologist since you will be using a library for that but some basic crypto knowledge might make some things easier.
* '''Implementation Languages:''' Java
* '''Mentor:''' Daniel Gultsch - Maintainer of Conversations
* '''Contact details''': Chatroom at conversations@conference.siacs.eu

Navigation menu