Age | Commit message (Collapse) | Author |
|
|
|
This was left over from an early draft of the microdescriptor code; it
began to populate the signatures array of a networkstatus vote, even
though there's no actual need to do that for a vote.
|
|
|
|
|
|
|
|
This means we need to handle the existence of multiple flavors of signature
in a detached signatures document, generate them correctly, and so on.
|
|
This patch introduces a new type called document_signature_t to represent the
signature of a consensus document. Now, each consensus document can have up
to one document signature per voter per digest algorithm. Also, each
detached-signatures document can have up to one signature per <voter,
algorithm, flavor>.
|
|
The consensus documents are not signed properly, not served, and not
exchanged yet.
|
|
|
|
This is a possible fix for bug 1023, where if we vote (or make a v2
consensus networkstatus) right after we come online, we can call
rep_hist_note_router_unreachable() on every router we haven't connected
to yet, and thereby make all their uptime values reset.
|
|
Directory authorities now reject Tor relays with versions less than
0.1.2.14. This step cuts out four relays from the current network,
none of which are very big.
|
|
This was the only log notice that happened during other
tor invocations, like --verify-config and --list-fingerprint.
Plus, now we think it works, so no need to hear about it.
|
|
documentation fix for get_uint64
remove extra "." from a log line
fix a long line
|
|
finishes the authority-operator interface side of proposal 167.
|
|
Big thanks to nickm and arma for helping me with this!
|
|
|
|
|
|
The more verbose logs that were added in ee58153 also include a string
that might not have been initialized. This can lead to segfaults, e.g.,
when setting up private Tor networks. Initialize this string with NULL.
|
|
|
|
|
|
Also div vote and other bandwidth by 1000, not 1024.
|
|
|
|
it never really worked, and hasn't been used for years.
|
|
|
|
whenever we remove a relay from the main routerlist, tell the
rephist module that it's no longer running.
|
|
tell the rephist module that a given relay is down whenever
we determine that it's down, not just when we thought it used
to be up.
|
|
|
|
|
|
Supporting the old formats made our code complex; running without them
has been discouraged since 0.2.1.x.
|
|
|
|
|
|
bytes (aka 20KB/s), to match our documentation. Also update
directory authorities so they always assign the Fast flag to relays
with 20KB/s of capacity. Now people running relays won't suddenly
find themselves not seeing any use, if the network gets faster
on average.
svn:r19305
|
|
to help track whether we received them when a relay operator claims
they got sent.
svn:r19213
|
|
send_unencrypted==0 correctly. Irrelevant, since we will soon never send them at all.
svn:r17953
|
|
descriptors shortly after startup, and then briefly resume
after a new bandwidth test and/or after publishing a new bridge
descriptor. Bridge users that try to bootstrap from them would
get a recent networkstatus but would get descriptors from up to
18 hours earlier, meaning most of the descriptors were obsolete
already. Reported by Tas; bugfix on 0.2.0.13-alpha.
svn:r17920
|
|
remain, though.
svn:r17888
|
|
The subversion $Id$ fields made every commit force a rebuild of
whatever file got committed. They were not actually useful for
telling the version of Tor files in the wild.
svn:r17867
|
|
vote it as Stable.
svn:r17821
|
|
documentation: Don't introduce two parameters called n when you're calling an algorithm O(n).
svn:r17783
|
|
svn:r17754
|
|
svn:r17739
|
|
svn:r17734
|
|
shahn: "Add some documentation for the WRA_* family of functions, also make
sure that (hopefully) all functions that return was_router_added_t
don't return ints directly and that they don't refer to integers in
their documentation anymore."
svn:r17731
|
|
comments so that they will get recognized as doxygen.
svn:r17729
|
|
svn:r17727
|
|
more extreme happens. the default should be to be quiet unless
something more extreme happens.
at least, this doesn't generate complaints anymore. perhaps that
means it is working better? :)
svn:r17724
|
|
svn:r17722
|
|
svn:r17721
|
|
svn:r17720
|
|
patch.
svn:r17686
|