YGGverse/aquatic
1
0
Fork 0
mirror of https://github.com/YGGverse/aquatic.git synced 2026-03-31 17:55:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update TODO with info about connection obfuscation extension

Browse source
This commit is contained in:
Joakim Frostegård 2020-07-04 19:58:26 +02:00
parent 76a340574e
commit 9443082575
1 changed files with 6 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
TODO.md
View file

@ -13,7 +13,6 @@
* non-compact peers for ipv6 generally: use ResponsePeerList enum * non-compact peers for ipv6 generally: use ResponsePeerList enum
* on ipv6, compact=1 should result in error response * on ipv6, compact=1 should result in error response
* on ipv4, compact=0 should result in error response * on ipv4, compact=0 should result in error response
* what does supportcrypto key do? Request upgrade to TLS?
### less important ### less important
* request parsing in protocol module instead of in network, maybe from byte * request parsing in protocol module instead of in network, maybe from byte
@ -28,6 +27,12 @@
positive number. positive number.
* handle_connection_read_event: this is an ugly function, but I don't know * handle_connection_read_event: this is an ugly function, but I don't know
how to improve it how to improve it
* Support supportcrypto/requirecrypto keys? Official extension according to
https://wiki.theory.org/index.php/BitTorrentSpecification#Connection_Obfuscation.
More info: http://wiki.vuze.com/w/Message_Stream_Encryption. The tricky part
is finding supportcrypto peers (and even better requirecrypto peers) to send
back to requirecrypto peers. Doesn't really work according to reference in
https://en.wikipedia.org/wiki/BitTorrent_protocol_encryption
## aquatic_ws ## aquatic_ws
* is 'key' sent in announce request? if so, maybe handle it like in * is 'key' sent in announce request? if so, maybe handle it like in