torproject / tor Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ticket33029 043 02 #1691
Closed
Closed
Ticket33029 043 02 #1691
Conversation
Pull Request Test Coverage Report for Build 7922
|
armadev
suggested changes
Jan 28, 2020
In the commit message, s/seperate/separate/ and s/addresse/address/
1475457
to
225dedb
teor2345
reviewed
Jan 29, 2020
| !the_nodelist || !the_nodelist->node_addrs) { | ||
| return; | ||
| } | ||
| address_set_add(the_nodelist->node_addrs, addr); |
Your code will be slightly shorter if you do this check here:
Suggested change
| address_set_add(the_nodelist->node_addrs, addr); | |
| if (!tor_addr_is_null(addr)) | |
| address_set_add(the_nodelist->node_addrs, addr); |
teor2345
reviewed
Jan 29, 2020
| if (!the_nodelist || !the_nodelist->node_addrs) { | ||
| return; | ||
| } | ||
| address_set_add_ipv4h(the_nodelist->node_addrs, addr); |
Your code will be slightly shorter if you do this check here:
Suggested change
| address_set_add_ipv4h(the_nodelist->node_addrs, addr); | |
| if (addr) | |
| address_set_add_ipv4h(the_nodelist->node_addrs, addr); |
cd539df
to
8373232
That function is only used to test the global bucket write limit for a directory connection. It should _not_ be used for anything else since that function looks to see if we are a directory authority. Rename it to something more meaningful. No change in behavior at this commit, only renaming. Part of #33029 Signed-off-by: David Goulet <dgoulet@torproject.org>
…_low() Signed-off-by: David Goulet <dgoulet@torproject.org>
Signed-off-by: David Goulet <dgoulet@torproject.org>
We separate v4 and v6 because we often use an IPv4 address represented with a uint32_t instead of a tor_addr_t. This will be used to also add the trusted directory addresses taken from the configuration. The trusted directories from the consensus are already added to the address set from their descriptor. Signed-off-by: David Goulet <dgoulet@torproject.org>
The configured, within the torrc or hardcoded, directory authorities addresses are now added to the nodelist address set. Signed-off-by: David Goulet <dgoulet@torproject.org>
Authorities were never sending back 503 error code because by design they should be able to always answer directory requests regardless of bandwidth capacity. However, that recently backfired because of a large number of requests from unknown source using the DirPort that are _not_ getting their 503 code which overloaded the DirPort leading to the authority to be unable to answer to its fellow authorities. This is not a complete solution to the problem but it will help ease off the load on the authority side by sending back 503 codes *unless* the connection is from a known relay or an authority. Fixes #33029 Signed-off-by: David Goulet <dgoulet@torproject.org>
This controls the previous feature added that makes dirauth send back a 503 error code on non relay connections if under bandwidth pressure. Signed-off-by: David Goulet <dgoulet@torproject.org>
Part of #33029 Signed-off-by: David Goulet <dgoulet@torproject.org>
Signed-off-by: David Goulet <dgoulet@torproject.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
No description provided.
The text was updated successfully, but these errors were encountered: