| Age | Commit message (Collapse) | Author |
|---|
|
|
|
`new_nonce` has been an alias for `random_nonce` for a while now. Having
two names for the same operation is confusing. `random_nonce` better
expresses the intent. The documentation for `new_nonce` talks about
guaranteeing that the nonce is different from previous ones, which is
incorrect, it's just quite likely to be different.
|
|
It is still C code, so still compatible with C compilers as well. This
change lets us see more clearly where implicit conversions occur by
making them explicit.
|
|
In the future, all TODOs added either need a bug number (TODO(#NN)) or a
person's github user name. By default, I made irungentoo the owner of
all toxcore TODOs, mannol the owner of toxav TODOs, and myself the owner
of API TODOs.
|
|
This header is a requirement for the public API, therefore is assumed to
exist. It is a C99 standard library header, and _Bool is not intended to
be used directly, except in legacy code that defines bool (and
true/false) itself. We don't use or depend on such code. None of our
client code uses or depends on such code. There is no reason to not use
bool.
|
|
It now enforces a bit more formatting. In particular, padding inside
parentheses is removed. I would like it to remove padding after unary
operators, but there seems to be no option for that.
|
|
1. Current module (if C file).
2. Headers from current library.
3. Headers from other library (e.g. toxcore includes in toxav).
4. System headers.
|
|
Messenger is slightly twisty when it comes to sending connection status
callbacks It will very likely need at the very least a partial refactor to
clean it up a bit. Toxcore shouldn't need void *userdata as deep as is
currently does.
(amend 1) Because of the nature of toxcore connection callbacks, I decided to
change this commit from statelessness for connections changes to statelessness
for friend requests. It's simpler this was and doesn't include doing anything
foolish in the time between commits.
group fixup because grayhatter doesn't want to do it
"arguably correct" is not how you write security sensitive code
Clear a compiler warning about types within a function.
|
|
http://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code
|
|
|
|
|
|
|
|
See #27 and #40 for details.
|
|
|
|
|
|
fix: make increment_nonce & increment_nonce_number independent of user-controlled input
fix: make crypto_core more stable agains null ptr dereference
|
|
|
|
|
|
|
|
Feed better nodes to onion, bootstrap off close clients when DHT friend is added.
|
|
Some test fixes.
|
|
on LAN.
|
|
|
|
|
|
|
|
|
|
|
|
Added a function to enable and disable TCP onion connections.
|
|
TODO:
-Reconnection.
-If UDP connction is good, connect to less TCP relays.
-Store some TCP relays in friend connection associated to each friend?
|
|
Attempted fix of connection checking to make it more stable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Check if onion data will be sent before encrypting it, not after.
|
|
Rename array in Node_format from client_id to public_key.
|
|
|
|
|
|
nodes and don't update them.
Paths now try to use the same TCP node for their entire lifetime.
|
|
This commit makes tox use one Onion_Client_Paths struct for all
friends instead of one per friend.
This should lower the number of ips tox sends packets to which is
what I think causes the router issues.
|
|
Assume nodes we manage to connect to with TCP are good to use for
the onion.
|
|
|
|
|
|
Try to make it more stable.
|
|
Put bootstrap nodes in a separate list than known good nodes.
|
|
|
