From 81983b98a24656af3cb907e20f5cc881f05cae11 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joakim=20Frosteg=C3=A5rd?= Date: Thu, 2 Jul 2020 21:16:13 +0200 Subject: [PATCH] Update TODO --- TODO.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/TODO.md b/TODO.md index fce335f..6a48d4a 100644 --- a/TODO.md +++ b/TODO.md @@ -7,9 +7,7 @@ ## aquatic_http * handshake stuff - * fix overcomplicated and probably incorrect implementation - * support TLS and plain at the same time?? - * really close connections after sending response?? + * fix overcomplicated and possibly incorrect implementation * fixed size buffer is probably bad * compact peer representation in announce response: is implementation correct? * scrape info hash parsing: multiple ought to be accepted @@ -110,6 +108,12 @@ just like best results in last benchmark, multiple client ips=true: * target-cpu=skylake: 439k * no target-cpu set: 388k +## aquatic_http / aquatic_ws +* Shared state for HTTP with and without TLS. Peers who announce over TLS + should be able to expect that someone snooping on the connection can't + connect them to a info hash. If someone receives their IP in a response + while announcing without TLS, this expectation would be broken. + ## aquatic_udp * Other HashMap hashers (such as SeaHash): seemingly not worthwhile, see