Timeline for How does Tor obfs4 protocol and PTs work?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2017 at 17:33 | comment | added | joncam | We are also trying to make a clear on-ramp-y description for developers with some scripts and walk-throughs at pluggabletransports.info ; see in particular pluggabletransports.info/transports and pluggabletransports.info/implement -- we'd love feedback at github.com/OpenInternet/PT-website | |
| Sep 12, 2016 at 4:45 | history | edited | cacahuatl | CC BY-SA 3.0 |
tried to update it to match the points made by Yawning.
|
| Sep 11, 2016 at 17:31 | vote | accept | user4191887 | ||
| Sep 11, 2016 at 2:51 | comment | added | user78 | ScrambleSuit does not obfuscate timing by default, and does not obfuscate packet size, just burst size. obfs4 obfuscates burst size, and can (at a performance penalty) obfuscate packet size. Basically obfs4 provides equivalent features to ScrambleSuit, and can be configured to do more. | |
| Sep 9, 2016 at 6:48 | comment | added | m894v5n74v539nm8 | And the fact that the destination IP of a guard relay is in the data packet, that should have been obvious to me. | |
| Sep 9, 2016 at 6:36 | comment | added | m894v5n74v539nm8 | Hmm I learn something today through this! It makes sense how Tor networks' exchange of cipher and it's metadata would be pretty unique. Wasn't able to think of it in that way initially on my answer here. | |
| Sep 9, 2016 at 4:11 | history | edited | cacahuatl | CC BY-SA 3.0 |
question seemed to be asking about "how they worked", so address architecture
|
| Sep 9, 2016 at 3:44 | history | answered | cacahuatl | CC BY-SA 3.0 |