presentations

Presentations
Log | Files | Refs

conclusion (2166B)

      1 * Conclusion and Future Work
      2 
      3 The implementation of Secure Share contributes to the efforts of creating a
      4 privacy protecting peer-to-peer social network. The client API provided as a
      5 library allows for creating various client applications right away, while the
      6 lower layers of the system are worked out.
      7 
      8 By implementing psycd as a service for the GNUnet framework, it allows us to
      9 benefit from GNUnet's modular architecture, which can be extended with new or
     10 improved routing schemes in future versions. The DV and mesh service are areas
     11 which need improvement. We need to have proper multicast message distribution in
     12 the network, and the mesh service is a promising candidate for that. It
     13 implements multicast groups, but group encryption still has to be implemented
     14 for this service. Thus improvements on the routing level are necessary to make
     15 the system really scalable and privacy protecting.
     16 
     17 As the implementation is still in a prototype stage, further work is needed to
     18 enhance the functionality of the system. Areas that need more work are:
     19 
     20 - improve the functionality and usability of the user interface, e.g. add
     21   dialogs for friendship establishment, and add different interfaces for different
     22   types of channels, e.g. status updates.
     23 - implement dedicated groups independent of person entities
     24 - user identities should be decoupled from node identities by assigning separate
     25   keys to users, so they have a master key and subkeys for their devices
     26 - file transfer over PSYC, this requires splitting large packets into smaller
     27   fragments and reassembling them when receiving
     28 - add UNIX socket support to psycd, as currently only TCP sockets are supported
     29   for clients
     30 - TLS sockets could be added later as well to enable secure connection to a
     31   remote node in case a local installation is not available
     32 - make the system work on mobile devices -- this could be done either via
     33   setting up a GNUnet node on the device or via establishing a TLS connection to
     34   a remote node; this also requires developing a user interface specifically
     35   designed for mobile devices
     36 - implement a web interface
     37 - implement testing using the GNUnet testing library