StarMirror/toxcore
1
0
Fork 0
mirror of https://github.com/irungentoo/toxcore.git synced 2024-03-22 13:30:51 +08:00
Code Issues Projects Releases Wiki Activity

Merge pull request #12 from mehrzad/master

Browse Source 
Cleaned up the README - mehrzad
This commit is contained in:
Magmus 2013-06-25 16:03:58 -07:00
commit f9d543819b
1 changed files with 24 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
README.md
View File

@ -2,47 +2,47 @@ Tox
===
Current IRC: #InsertProjectNameHere
on freenode or https://webchat.freenode.net/
on Freenode or [webchat](https://webchat.freenode.net/)
Proposal of a free as in freedom skype replacement:
--------Basics--------:
## Basics:
-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)
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)
-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?))
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?))
-Use something torrent DHT style so that peers can find the ip of the other peers when they have their id.
Use something torrent DHT style so that peers can find the ip of the other peers when they have their id.
-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.)
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.)
-When both peers are securely connected with AES they can securely exchange messages, initiate a video chat, send files, etc...
When both peers are securely connected with AES they can securely exchange messages, initiate a video chat, send files, etc...
-Your client stores the id of the peers along with their public keys used to initiate the connection (this is your contacts list)
Your client stores the id of the peers along with their public keys used to initiate the connection (this is your contacts list)
-------Roadmap------:
## Roadmap:
1.Get our DHT working perfectly.
2.Connection to other peers according to client id.
NOTE: We have not decided on the encryption yet. This was just a quick guess.
3.Encrypted message sending with RSA
4.Encrypted message sending with AES (encryption done)
5.Reliable sending of data larger than the maximum packet size.
...
1. Get our DHT working perfectly.
2. Connection to other peers according to client id.
NOTE: We have not decided on the encryption yet. This was just a quick guess.
3. Encrypted message sending with RSA
4. Encrypted message sending with AES (encryption done)
5. Reliable sending of data larger than the maximum packet size.
...
-------TODO-------:
## TODO:
See: docs/TODO.txt
See: docs/TODO.txt
-------Important-stuff--:
### Important-stuff:
Use the same UDP socket for everything
Use the same UDP socket for everything
-------Details---------:
### Details:
DHT protocol:
DHT protocol:
see: docs/DHT.txt