Saturday, 20 June 2015

Lets-Chat : Weekly update #5


Lets-chat





Here is my weekly update for GSoC project under +Tong Hui and +Mario Behling 





Issue #8 : Key generation for group OTR chat [1] 




  • Implemented the fingerprint of key using SHA-1 

  • Implemented the fingerprint of key using SHA-256

  • Implemented the fingerprints thus generated as 4 digit hex format

  • I will be pushing the fingerprints as 8-digit hex format in my next commit

  • Figured out that use of regex, instead of the loop I am using would be better as seen in TODO in my this week's commit 

  • Initially I was using nested loops to implement 4 digit hex format which I reduced to a loop for reducing complexity

  • Output is attached at [1]  as well as below for quick reference









Issue #19 Cannot create and enter in room [2]



  • +Tong Hui raised this bug , it was because of my commits that I pushed for Issue #17 generated by me

  • Fixed this bug

  • Closed Issue #19


Issue #17  [3]


  • I raised this issue as I felt it would be better for users to have password protected rooms by default

  • I pushed changed for this issue, but somehow it is giving a bug raised in Issue #19 at the moment



Issue #16 [4]


  • I raised this issue earlier, I tested it, worked fine

  •  +Tong Hui tested it as well and we have closed this one :)



I plan to work on Issue #15 [5] , I have already pushed some work :) and as suggested by my mentor +Tong Hui 





Saturday, 13 June 2015

Lets-chat : Weekly update #4

Lets - chat 




Here is my weekly update for GSoC project under +Tong Hui and +Mario Behling 





Issue #8 


  • Added execution time 
  • Made the key length as 1536 bits as required for OTR encryption
  • Planing to implement fingerprint of the key as suggested by my mentor +Tong Hui 


You can go through this issue at [1], and could see the snapshots of the terminal output after each commit for reference.





Issue  #15 




  • Raised this issue to implement encryption and decryption for OTR
  • Implemented Hash algorithm using crypto. SHA 512 using the private hex key generated by Diffie Hellman last week by me
  • Implemented AES encryption decryption on a sample text using Hmac . 



I am planing to work on improving issue #15 this week. [2] 






Issue #16



  • Raised this issue to have some more quotes for raptorize plugin 
  • Using this, when any of those quotes are messaged, a dinosaur appears which is quite interactive for end users
  • Added some frequently used words to raptorize 




[1]  https://github.com/beijinglug/lets-chat/issues/8
[2]  https://github.com/beijinglug/lets-chat/issues/15

Friday, 5 June 2015

Lets-chat : Weekly update GSoC #3

Lets-chat 



Here is the weekly update for my GSoC project, lets-chat under +Tong Hui and +Mario Behling 

  • Key - Generation : Issue #8 [1] 
As you could see, I initially used tried using random number generator [2] 








Then, I planned to use hardcore value : Number.MAX_VALUE and Number.MIN_VALUE instead of digits .  [3]









Later, I implemented key generation using crypto-js libraries [4] through Diffie Hellman as shown below :







Crypto-js libraries can be accessed at [5]

And later increased the key length as could be seen :









And added execution time [6]








Apart from Issue #8, I contributed to other issues as well :




Issue #10 [7] 

  • Issue #10 involved adding quick icons for reference, I provided one for key generation [8]




Issue #9 [9]
  • Issue #9 involves adding a menu for group encryption. There was a syntax error which I fixed. [10]


Issue #12 [11]

  • I raised this issue to have localised date in transcript. [12]


Issue #11 [13]

  • I raised this issue in order to have some hot keys in lets-chat. It is in progress, not yet resolved. 





[1]  https://github.com/beijinglug/lets-chat/issues/8

[2] https://github.com/beijinglug/lets-chat/commit/e71a1edb04d759914985c9df266f94bb9b147de6

[3]   https://github.com/beijinglug/lets-chat/commit/73074b0f0ec644074a3f40898f529939a42583d8

[4]  https://github.com/beijinglug/lets-chat/commit/77fe5f222bb8b20349c8f5e23862e59941c9c431

[5]  https://github.com/beijinglug/lets-chat/commit/4ef29d319b59640947f60873f6e7dd9c7fa930d2

[6]  https://github.com/beijinglug/lets-chat/commit/d2f6668e89ccfb439483b62d393184b522d7f9f9

[7]  https://github.com/fallacy321/lets-chat/commit/f19a99827d81536ccfb698478d0e9f28daef0b6d

[8]  https://github.com/beijinglug/lets-chat/issues/10

[9] https://github.com/fallacy321/lets-chat/commit/a370fc3b6dc61f63b178c705b462bf98b90ca174

[10]  https://github.com/beijinglug/lets-chat/issues/9

[11]  https://github.com/beijinglug/lets-chat/issues/12

[12] https://github.com/fallacy321/lets-chat/commit/6ed2ff992e4cf8b5f8d62ba05de0a7efd0b70e07

[13] https://github.com/beijinglug/lets-chat/issues/11