| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
Add logging when SSL verification fails, and discard the download
TODO: determine if we should make more noise
|
| |
|
|
| |
add import ssl...
|
| |
|
|
|
|
|
| |
It turns out that a self-signed cert will work just fine if it is
in the ca_certs file.
TODO: find some way of verifying this is the right cert :-)
|
| |
|
|
| |
Place the opener registration call somewhere after the class definition.
|
| |
|
|
|
|
|
|
|
|
|
| |
The blog post at:
http://thejosephturner.com/blog/2011/03/19/\
https-certificate-verification-in-python-with-urllib2/
describes how to do HTTPS certificate verification with urllib2
Note: it seems that the self-signed cert used does not have a CA; we
will need to resolve this.
|
| |
|
|
| |
I mean hey, maybe not everyone can rollerskate on multidementianal surfaces..
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also, clarify the startup false positive test.
|
| |
|
|
|
|
|
| |
This commit provides analysis to guide parameter choices for the path bias
defense. It contains a standalone attack and defense simulation script, a
results.txt with example output, and an observations.txt with comments to
help work towards an answer for #6135.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use unfiltered bandwidth because I suspect we're being too generous to fast
nodes. To get more feedback, they should have to have spare capacity all the
time, not just sometimes.
However, gimpy nodes will still get to use filtered bandwidth if we've
punished them too much already.
Also, circuit failures now target a 0% rate (full success) instead of the
network average, but the penalty only applies if you fall below the network
average for your node class.
|
| | |
| |
| |
| | |
Also, log node class when we cap, and in some other cases.
|
| |/ |
|
| |
|
|
| |
Too bad python doesn't seem to have constants for either?
|
| |
|
|
|
|
|
|
| |
Tor internally multiplies our values by 1000, and silently eats the overflow.
Why do we bother dividing them by 1000 in the first place? It just causes
confusion and bugs.. The git blame log and comments mumble something about
consensus diffs, but I think we gave up on those...
|
| |
|
|
| |
Also don't use Wgd in mercy mode or in section2 mode.
|
| | |
|
| | |
|
| |
|
|
|
| |
I think this was added because circ_fail_rate used to get set to 0 by a
consensus param that we later changed.
|
| |
|
|
|
| |
I want to try to disable it and see if these become more even
or not.
|
| | |
|
| | |
|
| |
|
|
| |
Also demote a couple logs, and add a couple more.
|
| |
|
|
|
| |
This seems to only take a few seconds to do.. Expensive, but probably not
prohibitively so?
|
| |
|
|
|
| |
We can just check to see if we've previously punished the node by inspecting
the previous values directly. Forgot about that.
|
| |
|
|
|
|
| |
If the param is set, we don't accumulate negative pid_error_sum for nodes with
negative pid_error. Prevents us from punishing these nodes to 0 bw. The param
only makes sense for descriptor-based feedback.
|
| |
|
|
|
| |
Intuitively, it seems to make sense to exclude nodes with no chance
of reaching the setpoint from consideration.
|
| |
|
|
| |
Otherwise we might not detect CPU overload conditions in them.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Let's try computing a second error and take their sum.
|
| |
|
|
| |
Governed by consensus param (off by default).
|
| |
|
|
|
|
| |
These defaults should still be equivalent to Section 2 in the spec, but
these values will keep the PID interim state from disappearing every
time ides crashes and the consensus params disappear.
|
| |
|
|
|
| |
We have a cap+log warn below that we will hit in this case
instead of crashing.
|
| | |
|
| | |
|
| |
|
|
| |
Also correct log line.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
Memory-only sqlite might make them more bearable.
|
| | |
| |
| |
| |
| | |
These are still subject to change, especially in terms
of defaults.
|
| | |
| |
| |
| |
| | |
It may be equivalent to NS bw, since the NS bw functions as an accumulator..
We may want to set T_i_decay to 0 for this code.
|