Changes

Jump to navigation Jump to search
m
no edit summary
Line 1: Line 1:  
== Introduction ==
 
== Introduction ==
This project aims to create fully-featured implementation of experimental Encrypted Sessions ([http://xmpp.org/extensions/xep-0116.html XEP-0116]) enhancement of XMPP protocol into multi-IM client [http://sim-im.org/ SIM-IM]. During the course of development, I also plan to fix bugs present in XMPP support in SIM (basic working XMPP support is there, contrary to what name of this project would suggest), as well as add new features that will improve usability of XMPP support in this client (administrator tools, better service support, presence detection fixes, fixes of more than one logins on one account, etc...). This will, however, be side effect of my work, main focus will remain on Encrypted sessions support, which is something that Jabber network presently lacks, because feel of security is essential for most power users and should be for all users, and Jabber network might not be accepted well by some people in that area (mostly unencrypted server-to-server links, jabber servers running on not completely trusted machines, etc.). It should be allowed to encrypt traffic in such manner that it is not decrypted (and decryptable) on any servers it passes on its way.  
+
This project aims to create fully-featured implementation of experimental Encrypted Sessions ([http://xmpp.org/extensions/xep-0116.html XEP-0116]) enhancement of XMPP protocol into multi-IM client [http://sim-im.org/ SIM-IM]. During the course of development, I also plan to fix bugs present in XMPP support in SIM (basic working XMPP support is there, contrary to what name of this project would suggest), as well as add new features that will improve usability of XMPP support in this client (administrator tools, better service support, presence detection fixes, fixes of more than one logins on one account, etc...). This will, however, be side effect of my work, main focus will remain on Encrypted sessions support, which is something that XMPP network presently lacks, because feel of security is essential for most power users and should be for all users, and XMPP network might not be accepted well by some people in that area (mostly unencrypted server-to-server links, XMPP servers running on not completely trusted machines, etc.). It should be allowed to encrypt traffic in such manner that it is not decrypted (and decryptable) on any servers it passes on its way.  
    
== Project schedule ==
 
== Project schedule ==
Line 18: Line 18:  
=== Week 3 (7.6. to 13.6.) ===  
 
=== Week 3 (7.6. to 13.6.) ===  
 
* Finally some free time, yet still mostly occupied by exams that will not end until late June. Still finishing projects. Aaargh :-(.  
 
* Finally some free time, yet still mostly occupied by exams that will not end until late June. Still finishing projects. Aaargh :-(.  
* I finally got thru reading both important XMPP RFCs and even better, I understood them and I found XMPP protocol even more capable and better than I first suspected. Well, XML namespace stuff is quite complicated (entire XML namespace model has been causing me headaches since I first stumbled upon it year ago, but it is powerful and well worth it), and I still don't remember URI of stream namespace. Fortunately, doesn't matter, that's what my pastefile is for ;-). I was then playing with my Jabber server via telnet and was disappointed to know that some things I learned just don't work there. Mainly SASL auth stuff... maybe that's better, I can't do CRAM-MD5 in my head anyway. So I went to observing XML console in Psi and Network monitor in SIM. I learned few things there, combined with looking up relevant XEPs that were in use there.  
+
* I finally got thru reading both important XMPP RFCs and even better, I understood them and I found XMPP protocol even more capable and better than I first suspected. Well, XML namespace stuff is quite complicated (entire XML namespace model has been causing me headaches since I first stumbled upon it year ago, but it is powerful and well worth it), and I still don't remember URI of stream namespace. Fortunately, doesn't matter, that's what my pastefile is for ;-). I was then playing with my XMPP server via telnet and was disappointed to know that some things I learned just don't work there. Mainly SASL auth stuff... maybe that's better, I can't do CRAM-MD5 in my head anyway. So I went to observing XML console in Psi and Network monitor in SIM. I learned few things there, combined with looking up relevant XEPs that were in use there.  
    
=== Week 4 (13.6. to 20.6.) ===
 
=== Week 4 (13.6. to 20.6.) ===
Line 25: Line 25:     
== Relevant links ==
 
== Relevant links ==
* [http://xmpp.org/extensions/xep-0116.html XEP-0116]
+
* [https://xmpp.org/extensions/xep-0116.html XEP-0116]
* [http://svn.berlios.de/wsvn/sim-im/branches/branch-QString/?rev=0&sc=0 WebSVN access to project repository]
+
* [https://svn.berlios.de/wsvn/sim-im/branches/branch-QString/?rev=0&sc=0 WebSVN access to project repository]
 
* Anonymous SVN access: svn://svn.berlios.de/sim-im/branches/branch-esession
 
* Anonymous SVN access: svn://svn.berlios.de/sim-im/branches/branch-esession
      −
* [http://www.ietf.org/rfc/rfc3920.txt XMPP Core RFC]
+
* [https://www.ietf.org/rfc/rfc3920.txt XMPP Core RFC]
* [http://www.ietf.org/rfc/rfc3921.txt XMPP IM & presence RFC]
+
* [https://www.ietf.org/rfc/rfc3921.txt XMPP IM & presence RFC]
* [http://xmpp.org/extensions/xep-0079.html Advanced Message Processing]
+
* [https://xmpp.org/extensions/xep-0079.html Advanced Message Processing]
    
[[Category:Summer of Code 2006]]
 
[[Category:Summer of Code 2006]]
190

edits

Navigation menu