spec
spec copied to clipboard
TokTok
Tox Protocol Specification
The **elliptic curve Diffie-Hellman** key exchange, especially one that's _ephemeral_, would encourage more secure message transport, than just describing the algorithm to be used as generic, non-ecliptic Diffie-Hellman.
Please consider using the signal and noise pipes protocols. Signal (formerly axolotl) and noise are very good protocols, well-reviewed and offering very desirable features that go beyond what otr has...
**Issue by [GrayHatter](https://github.com/GrayHatter)** _25 Oct 2016 at 22:26 UTC+2_ _Originally opened as https://github.com/TokTok/c-toxcore/issues/210_ ---- | Attacker goal | Security property | How ToxCore deals with that? | |------------------|-----------------------|----------------------------------------| | Compromise...
Would you please share with us a nice doc of how it is done? With links, math papers, how much time would it take to break the cipher, etc?
if the specfication could be more detailed, there would be getting more people involved in this project. And compared to the toxcore project one year ago, its decument does make...
I've read the spec and then looked at the c-toxcore implementation to double check if I understood it correctly, looks like I've got it right. ### The issue The thing...
I've been researching this related topics for a while and I have a concern regarding the onion path construction. Kind of related to #56, but from a different angle. ###...
Reading the spec I have a few more questions. I'll combine them into a single issue since they are related. The spec says that nodes for onion path include DHT...
Here is the quote from the spec: > If we are announcing ourselves we must put our real long term public key in the packet and encrypt it with our...