bahackers / gpg-group-chat Goto Github PK

The CI pipeline should have at least steps to run the unit tests and another to run the pep8

Implement a simple client that must connect to a gpg-group-chat server instance and send messages in plain text by now

More details #10

I want to rise a discussion about refactor our app to program in asynchronous way.

Since we are using Python 3.4 and just Python 3.5 will came with async syntax sugar, I am proposing to use Twisted

https://twistedmatrix.com/trac/

I want to know the team opinion about that.
@ruanLN @Dkmister @mateusriad @leormarqs @pfvscheffer

The client should encrypt every message before send to a server instance using GPG.

The messages can be encrypted to user's own key and its ID can be hard coded on code by now

More details #10

More details #10

We can consult some availables licenses on http://choosealicense.com/licenses/

Create a page when the user pass the --help paramenter

That message the client should send to server each 5 seconds.

The server should close the connection with the client that doesn't sent this notice in 1 minute

More details #10

Based on the team members discussion we have to implement the protocol to client - server communication.

This issue scope is to create a logic that identify the cases below and call a class responsible for that logic.

This issue scope doesn't cover implement all those cases logic.

The issues for implement the cases logic are:
Case1: #16
Case2: #11
Case3: #12
Case4: #13
Case5: #14
Case6: #15

Protocol cases:

Case 1 - new user ask to connect to the server:

• C -> S hello
• C -> S I am "nickname", "PGP key fingerprint"
• S -> C accepted or not accepted
• S -> users connected
• S -> C {[ "nick1": "fingerprint1", "nick2": "fingerprint2", ... ]}

Case 2 - notification that new user connects to the server:

• S -> C new user connected
• S -> C { "new_nick": "new_fingerprint" }

Case 3 - send message:

• C -> S send message
• C -> S block PGP message

Case 4 - receive message:

• S -> C receive message
• S -> C block PGP message

Case 5 - notification that user disconnects:

• S -> C user disconected
• S -> C "nickname"

Case 6 - keep alive notice:

• C -> S keep alive
• S -> C ok

More details #10

Create the project structure, dependency file, gitignore and so on

More details #10

Implement a simple server mode that by now, should just accept a connection and log on stdout every received message.

The configuration like listen port can be hard coded on the code by now