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

Added small things to readme.

Browse Source
This commit is contained in:
irungentoo 2013-06-25 20:41:13 -04:00
parent 14ab4c8745
commit f45e3c29a7
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -18,17 +18,17 @@ Use something torrent DHT style so that peers can find the ip of the other peers
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) 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.) (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 the encryption(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.(Done, needs large scale testing though.) 1. Get our DHT working perfectly.(Done, needs large scale testing though.)
2. Connection to other peers according to client id. 2. Reliable connection (See Lossless_UDP protocol) to other peers according to client id.
3. Encrypted message sending with RSA (NOTE: We have not decided on the encryption yet. This was just a quick guess.) 3. Encrypted message sending with RSA (NOTE: We have not decided on the encryption yet. This was just a quick guess.)
4. Encrypted message sending with AES (encryption done) 4. Encrypted message sending with AES (encryption done)
5. Reliable sending of data larger than the maximum packet size. 5. Reliable encrypted sending of data larger than the maximum packet size.
... ...
## TODO: ## TODO: