Here's a summary of the project's current status
1. Make the OTR plugin register an encryption button in the tool (Pending, see bellow) and menu (Implemented) bars of the chat window
Current implementation adds a button in the tool bar which is dummy for the time being. I'm not sure what this button should do. For example it could be a toggle button (start/stop encryption) or it could bring up the whole OTR menu.
2. The above mentioned button should indicate the status of the current chat (Implemented)
3. The above mentioned button should also contain (at least) the following options
* Start an ecnrypted chat (Implemented)
* End encrypted chat (Implemented)
* Authenticate/Verify contact (Implemented)
* Auto encrypt every session with this contact (Pending. This can only be set globally in the configuration form for the time being.)
* Help/ What is this (Implemented)
4. Implement support for clients that do not have OTR (Implemented)
5. Add support for incoming fragmented messages (Pending, otr4j has to be extended)
6. Configuration intertface that allows generating and displaying our own key as well as managing other people’s keys (Pending)
7. JUnit tests that run with every protocol (Pending)
otr4j is part of my GSoC 09' project and is encouraged by the SIP Communicator development. otr4j is an implementation of the OTR (Off-the-Record) protocol in java.
Tuesday, August 11, 2009
Subscribe to:
Post Comments (Atom)
My Commits to SIP Communicator
Error loading feed.
Mercurial commits to project otr4j on Google Code
- Revision 408c8043ee: Fixed a potential NullPointerException. - Invalid Date
- Revision 64379ae226: Changed some of the OtrEngine methods to throw OtrExceptions instead of calling - Invalid Date
- Revision 8810f92c65: Added tag 0.9 for changeset d59b314765cf - Invalid Date
- Revision d59b314765: # Fixed DataMessage serialization. # Issue 8: non-(ISO Latin 1) characters do no - Invalid Date
- Revision 0d25e99de9: Renamed MessageBase to AbstractMessage and EncodedMessageBase to AbstractEncoded - Invalid Date
No comments:
Post a Comment