2013-06-26 06:46:45 +08:00
Tox
2013-06-24 08:12:13 +08:00
===
2013-06-24 08:15:33 +08:00
2013-06-24 08:42:35 +08:00
Current IRC: #InsertProjectNameHere
2013-06-26 07:00:55 +08:00
on Freenode or [webchat ](https://webchat.freenode.net/ )
2013-06-24 08:42:35 +08:00
2013-06-24 08:15:33 +08:00
Proposal of a free as in freedom skype replacement:
2013-06-26 06:45:41 +08:00
## Basics:
2013-06-24 08:15:33 +08:00
2013-06-26 06:54:52 +08:00
UDP most be used for everything simply because you can't do hole punching with TCP (well you can but it doesn't work all the time)
2013-06-24 08:15:33 +08:00
2013-06-26 07:08:32 +08:00
Every peer is represented as a byte string (the client id) (it is the hash (SHA-256?) of the public key of the peer). (if you want to add someone you need that id (either ask that person directly or maybe through some kind of search engine?))
2013-06-24 08:15:33 +08:00
2013-06-26 06:54:52 +08:00
Use something torrent DHT style so that peers can find the ip of the other peers when they have their id.
2013-06-24 08:15:33 +08:00
2013-06-26 06:54:52 +08:00
Once the client has the ip of that peer they start initiating a secure connection with each other.(asymmetric encryption(RSA?) is used to encrypt the session keys for the symmetric(AES?) encryption so that they are exchanged securely)
(We can't use public key encryption for everything it's too fucking slow) man in the middle attacks are avoided because the id is the hash of the public key (the client can be sure it's legit.)
2013-06-24 08:15:33 +08:00
2013-06-26 08:41:13 +08:00
When both peers are securely connected with the encryption(AES?) they can securely exchange messages, initiate a video chat, send files, etc...
2013-06-24 08:15:33 +08:00
2013-06-26 06:54:52 +08:00
Your client stores the id of the peers along with their public keys used to initiate the connection (this is your contacts list)
2013-06-24 08:15:33 +08:00
2013-06-26 06:52:34 +08:00
## Roadmap:
2013-06-24 08:15:33 +08:00
2013-06-26 08:33:23 +08:00
1. Get our DHT working perfectly.(Done, needs large scale testing though.)
2013-06-26 08:41:13 +08:00
2. Reliable connection (See Lossless_UDP protocol) to other peers according to client id.
2013-06-26 08:33:23 +08:00
3. Encrypted message sending with RSA (NOTE: We have not decided on the encryption yet. This was just a quick guess.)
2013-06-26 07:00:07 +08:00
4. Encrypted message sending with AES (encryption done)
2013-06-26 08:41:13 +08:00
5. Reliable encrypted sending of data larger than the maximum packet size.
2013-06-26 07:00:07 +08:00
...
2013-06-24 08:15:33 +08:00
2013-06-26 06:52:34 +08:00
## TODO:
2013-06-26 05:16:45 +08:00
2013-06-26 07:08:32 +08:00
See: [docs/TODO.txt ](https://github.com/irungentoo/InsertProjectNameHere/blob/master/docs/TODO.txt )
2013-06-26 05:16:45 +08:00
2013-06-26 06:45:41 +08:00
### Important-stuff:
2013-06-24 08:15:33 +08:00
2013-06-26 06:54:52 +08:00
Use the same UDP socket for everything
2013-06-24 08:15:33 +08:00
2013-06-26 20:32:42 +08:00
Keep everything really simple.
2013-06-26 06:52:34 +08:00
### Details:
2013-06-24 08:15:33 +08:00
2013-06-26 06:54:52 +08:00
DHT protocol:
2013-06-26 07:08:32 +08:00
see: [docs/DHT.txt ](https://github.com/irungentoo/InsertProjectNameHere/blob/master/docs/DHT.txt )
2013-06-24 08:15:33 +08:00
2013-06-26 08:33:23 +08:00
Lossless UDP protocol:
Either we find one with an already working implementation (Preferred solution)
It should not be very hard to come up with one ourselves though if need be.
see also: [docs/Lossless_UDP.txt ](https://github.com/irungentoo/InsertProjectNameHere/blob/master/docs/Lossless_UDP.txt )
