Age | Commit message (Collapse) | Author |
|
|
|
Be more specific: clearly distinguish between uploaded and downloaded
votes.
Add the Tor version that introduces this behaviour.
Spec for ticket 4631.
|
|
|
|
Spec change for ticket #4631.
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
Part of 32695, closes 32955.
|
|
When we documented prop298 in dir-spec, we forgot the consensus
method summary.
Part of 28266.
|
|
This only adds newline characters to make the existing text blocks act like
"blockquote" or "code block" syntax in Markdown, asciidoc, and others.
This was accomplished by manually reviewing the output of this script:
```bash
for f in *.txt; do
cat $f | python -c "import sys,re;print(re.sub(r'(\n {0,3}[^ \n][^\n]*\n)( {4,}[^\n]*)', r'\1\n\2', sys.stdin.read()))" > ${f}.tmp
mv ${f}.tmp $f
done
```
|
|
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
The clear standard is trailing "." after each numeric section. This fixes
the small handful of outliers. This makes it easy to convert these headers
to common markup formats, for example:
http://hyperpolyglot.org/lightweight-markup
|
|
BridgeDB supports bridge-distribution lines since version 0.5.0:
<https://bugs.torproject.org/23957>
|
|
This bridge distribution method was never finished:
<https://bugs.torproject.org/22775>
|
|
Part of #30365
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
Part of 30224.
|
|
|
|
Part of 29959.
|
|
From Tor 0.4.0.4-alpha, bandwidth files are available via HTTP,
but the Tor version in which it first appeared was wrong.
Fixes #26694.
|
|
We increased the bandwidth statistics period in 23856 to improve privacy.
This change also increased the observed bandwidth period.
Closes bug 28984.
|
|
|
|
Closes #29147
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tor does not generate ns consensuses that are explicitly labelled as ns
consensuses. This updates the spec to make the flavor portion optional,
and to allow the assumption to be made that if a flavor is omitted from
the "network-status-version" line then it is "ns".
One "flavour" was also turned into a "flavor" for consistency.
|
|
The extra-info-digest field of server descriptors was defined to contain
either a SHA1, or a SHA1 and a SHA256 digest. These were both meant to
be computed over the same data but due to an implementation error, the
Tor network has been computing the digests over different data for a
while. This is a lot easier to fix in the spec than in the code, and
the error does not seem to cause any harm beyond being a little
confusing (which this patch should help with).
A minor fix is also made to the SHA1 digest portion of the text. This is
a typo fix and a clarification, and does not change the semantic meaning
for that portion.
|
|
Remove the header's Keywords in the bandwidth-file-headers item,
since they are described in bandwidth-file-spec.txt and we should
not need to update two specifications every time they change.
|
|
Closes 26827.
|
|
|
|
|
|
Closes 26799.
|
|
* dir-spec: don't post bandwidth files to other authorities
* dir-spec: add URL for current bandwidth file
* dir-spec: clean up the consensus and vote "current" publication schedule
Closes ticket #21377.
|
|
In a similar ways as authorities expose the votes for the next
consensus.
This way it can be archived by CollectTor
|
|
|
|
|
|
|
|
|
|
|
|
to bandwidth-file-headers
|
|
ArgumentChar is already defined in 1.2.
Also change definitions order.
|
|
|
|
|
|
|
|
Paragraph on events required to update descriptor were not reflecting
changes made in #23856 where the bandwidth changes need to happen
in a time interval of 3h instead of 20min.
|
|
The descriptor would be updated on bandwidth changes only when
the uptime is less than 24h.
|
|
|
|
also change version of Tor where 1st appeared.
|